• Resolved asdecopes

    (@asdecopes)


    Hi,
    I’ve been using your plugin for the last 3 or 4 Euros/WM.. Thanks!

    Now I have a litte problem. After updating the first match Qatar-Ecuador. I recive the following error:

    In the wordpress GUI:
    Step ‘question_scores’: Something went wrong while (re)calculating the scores. See the help page for details on solving this problem.

    In Apache logfile:
    “WordPress database error Unknown column ‘joker_used’ in ‘field list’ for query INSERT INTO pool_mukp_scorehistory_s1_t2\r\n\t\t\t\t\t\t\t\t\t\t( ranking_id,…………”

    Plugin version: Last one, updated from the last Eurocup.
    Wordpress version: Last one.

    Thanks in advance.

    AsDeCopes

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author AntoineH

    (@antoineh)

    Looks like the last update did not update your database. If you run the following script via a tool like phpMyAdmin, then this error should be resolved.

    ALTER TABLE pool_mukp_predictions CHANGE home_score home_score TINYINT UNSIGNED NULL, CHANGE away_score away_score TINYINT UNSIGNED NULL;
    
    DROP TABLE pool_mukp_scorehistory_s1_t1; 
    
    DROP TABLE pool_mukp_scorehistory_s1_t2; 
    
    CREATE TABLE IF NOT EXISTS pool_mukp_scorehistory_s1_t1 ( ranking_id INT UNSIGNED NOT NULL, score_order INT UNSIGNED NOT NULL DEFAULT '0', type TINYINT UNSIGNED NOT NULL DEFAULT '0', score_date DATETIME NOT NULL, source_id INT UNSIGNED NOT NULL, user_id INT UNSIGNED NOT NULL, score INT UNSIGNED NOT NULL, full SMALLINT UNSIGNED NOT NULL DEFAULT '0', toto SMALLINT UNSIGNED NOT NULL DEFAULT '0', goal_bonus SMALLINT UNSIGNED NOT NULL DEFAULT '0', goal_diff_bonus SMALLINT UNSIGNED NOT NULL DEFAULT '0', joker_used SMALLINT UNSIGNED NOT NULL DEFAULT '0', total_score INT UNSIGNED NOT NULL DEFAULT '0', ranking INT UNSIGNED NOT NULL, PRIMARY KEY (ranking_id,type,source_id,user_id), KEY ix_ranking_score_order_user (ranking_id,score_order,user_id) USING BTREE, KEY ix_user_id (user_id) USING BTREE, KEY ix_ranking_id (ranking_id) USING BTREE, KEY ix_ranking (ranking) USING BTREE, KEY ix_score_order (score_order) USING BTREE, KEY ix_joker_used (joker_used) ) DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; 
    
    CREATE TABLE IF NOT EXISTS pool_mukp_scorehistory_s1_t2 ( ranking_id INT UNSIGNED NOT NULL, score_order INT UNSIGNED NOT NULL DEFAULT '0', type TINYINT UNSIGNED NOT NULL DEFAULT '0', score_date DATETIME NOT NULL, source_id INT UNSIGNED NOT NULL, user_id INT UNSIGNED NOT NULL, score INT UNSIGNED NOT NULL, full SMALLINT UNSIGNED NOT NULL DEFAULT '0', toto SMALLINT UNSIGNED NOT NULL DEFAULT '0', goal_bonus SMALLINT UNSIGNED NOT NULL DEFAULT '0', goal_diff_bonus SMALLINT UNSIGNED NOT NULL DEFAULT '0', joker_used SMALLINT UNSIGNED NOT NULL DEFAULT '0', total_score INT UNSIGNED NOT NULL DEFAULT '0', ranking INT UNSIGNED NOT NULL, PRIMARY KEY (ranking_id,type,source_id,user_id), KEY ix_ranking_score_order_user (ranking_id,score_order,user_id) USING BTREE, KEY ix_user_id (user_id) USING BTREE, KEY ix_ranking_id (ranking_id) USING BTREE, KEY ix_ranking (ranking) USING BTREE, KEY ix_score_order (score_order) USING BTREE, KEY ix_joker_used (joker_used) ) DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
    • This reply was modified 3 years, 5 months ago by AntoineH. Reason: too many backticks messed up the layout
    Thread Starter asdecopes

    (@asdecopes)

    Perfect. It worked perfeclty!

    many thanks!

    Kind regads,
    AsDecopes

    • This reply was modified 3 years, 5 months ago by asdecopes.
Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Error calculating ranking’ is closed to new replies.