Multisite and Database prefixes
-
On wp-security-core.php, shouldn’t you declare the database tables using $wpdb->base_prefix, instead of $wpdb->prefix? If you use the latter It will cause the code to sometimes use a multisite prefix (wp_20_) instead of the main one (wp_)
-
Hi,
I don’t exactly know in which page it happen so I don’t know the circumstance but I had lots of these in the error log:
WordPress database error Table 'db.wp_89_aiowps_login_lockdown' doesn't exist for query SELECT * FROM wp_89_aiowps_login_lockdown WHERE release_date > '2018-06-26 14:31:20' AND failed_login_ip LIKE '***.***.***%' made by wp_signon, wp_authenticate, apply_filters('authenticate'), WP_Hook->apply_filters, AIOWPSecurity_User_Login->block_ip_if_locked, AIOWPSecurity_User_Login->check_locked_useror
WordPress database error Table 'db.wp_164_aiowps_login_activity' doesn't exist for query SHOW FULL COLUMNS FROM 'wp_164_aiowps_login_activity' made by wp_clear_auth_cookie, do_action('clear_auth_cookie'), WP_Hook->do_action, WP_Hook->apply_filters, AIOWPSecurity_User_Login->wp_logout_action_handlerIt seems its querying data within the scope of one of the network’s websites, and since the tables only exist at a root level, it cannot find them.
That’s why i suggested that if, by design, the aiowps tables only exist at a root level, then declaring their names into a constant should be done using base_prefix which is always the root prefix, multisite or not.
Hope this helps.
- The topic ‘Multisite and Database prefixes’ is closed to new replies.
