FULLTEXT indexes still causing a problem

  • Resolved simonmm

    (@simonmm)


    8 years, 1 month ago

    MySQL 5.6.34, PHP 5.6.27, WP 4.6.1, WC 2.6.4

    After running a conversion and optimisation (after which all appears OK?), the php_error.log contained 14 instances of:

    
[18-Oct-2016 21:43:35 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '>table_name}' at line 6 for query SELECT
                        table_schema,
                        table_name
                        FROM information_schema.statistics
                        WHERE index_type = 'FULLTEXT'
                        AND table_name = {$row->table_name} made by do_action('wp_ajax_vevida-optimizer-convert-myisam-innodb'), call_user_func_array, vevida_optimizer_convert_myisam_innodb, vevida_convert_tables
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter simonmm

    (@simonmm)

    Oops, missed the critical bit of info – Vevida Optimizer v1.1.2

    Plugin Contributor Jan Reilink

    (@janr)

    Thank you for your notification @simonmm, we’ll investigate and get back to you as soon as possible.

    Plugin Contributor Jan Reilink

    (@janr)

    Thanks @simonmm, I’ve verified the bug. We’ll release a fix asap, for now you can edit wp-content/plugins/vevida-optimizer/plugins/convert.php, and remove the curly brackets on lines 75 and 81.

    {$wpdb->prefix}

    becomes

    $wpdb->prefix

    My apologies for the inconvenience.

    • This reply was modified 8 years, 1 month ago by Jan Reilink.
    • This reply was modified 8 years, 1 month ago by Jan Reilink. Reason: braces > curly brackets
    Plugin Contributor Jan Reilink

    (@janr)

    We’ve released version 1.1.4, addressing this issue.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘FULLTEXT indexes still causing a problem’ is closed to new replies.

Tags