• Resolved antennanl

    (@antennanl)


    Dear Jan,

    Our Apache error_log contains lines like:
    [Thu Feb 09 20:06:16 2017] [error] [client 192.168.1.51] WordPress database error Table 'my_prefix.wp_options' doesn't exist for query SHOW FULL COLUMNS FROMwp_options` made by
    require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_fun
    c_array, Wp_Sponsors_Admin->update, Wp_Sponsors_upgrade->run, Wp_Sponsors_upgrade->upgrade200, referer: http://www.website.org/gaf/`

    The file includes/class-wp-sponsors-upgrade.php calls for the wp_options table without using the variable table_prefix. Using such a WordPress Database Prefix is often advised as a good practice to improve safety against standard sql injections attempts. One can declare a value for this variable in wp_config.php.

    I hope a future release of this useful plugin can have a fix for this database error.

    Regards,

    Jay
    Antenna

Viewing 2 replies - 1 through 2 (of 2 total)
  • Agreed. Never make an assumption that someone else is going to have the same WordPress settings as you. I havn’t had much of a look at the plugin yet, but it’s not off to a great start, unfortunately. It sounded perfect from the description.

    Try:

    global $wpdb;
    echo "<p>The {$wpdb->prefix}_options table is not okay.</p>";

    -Amanda

    • This reply was modified 9 years, 1 month ago by m4ndi.
    • This reply was modified 9 years, 1 month ago by m4ndi.

    Hey there

    Yes, this is a pretty bad mistake on my part. I have to fix ready in a point release that should be out this weekend.

    Hope this doesn’t turn you away from trying the plugin.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Database error because of missing table_prefix’ is closed to new replies.