• I have been getting database errors that look like this:

    “WordPress database error Table ‘xxxxx.wp_options’ doesn’t exist for query delete from wp_options where option_name REGEXP ‘^_transient_wcj_product_by_user_role’ made by wp_untrash_post, do_action(‘untrash_post’), …”

    I have changed my prefix value for my WordPress tables from “wp_” to something else. However, it appears that the Booster routine includes/classes/class-wcj-module-product-by-condition.php still explicitly refers to the default “wp_options” table value on line #163 rather than using the “$wpdb->prefix . ‘options'” approach. I am using the latest 4.7.1 version of Booster.

  • The topic ‘Not using $wpdb->prefix on table’ is closed to new replies.