• Resolved Antipole

    (@antipole)


    Site is mg30.antipole.co.uk
    Hi… enjoying using the plug-in. But I note I am getting database errors. I thought it was because of the User Switching plug-in, but author John Blackbourn says:
    Hi Tony, the SQL errors you pasted are coming from All In One WP Security, not from User Switching. Sample log follows.
    Can you advise please? thanks.
    Mar 05, 14:39:22 WordPress database error Table ‘antipole_wp00.wp_12_aiowps_login_activity’ doesn’t exist for query UPDATE wp_12_aiowps_login_activity SET logout_date = ‘2014-03-05 14:39:22’ WHERE user_id = 2 AND login_ip = ‘109.158.111.61’ AND logout_date = ‘0000-00-00 00:00:00’ made by require(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, user_switching->action_init, switch_to_user, wp_clear_auth_cookie, do_action(‘clear_auth_cookie’), call_user_func_array, AIOWPSecurity_User_Login->wp_logout_action_handler
    Mar 05, 14:39:30 WordPress database error Table ‘antipole_wp00.wp_12_aiowps_login_activity’ doesn’t exist for query UPDATE wp_12_aiowps_login_activity SET logout_date = ‘2014-03-05 14:39:30’ WHERE user_id = 29 AND login_ip = ‘109.158.111.61’ AND logout_date = ‘0000-00-00 00:00:00’ made by require(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, user_switching->action_init, switch_to_user, wp_clear_auth_cookie, do_action(‘clear_auth_cookie’), call_user_func_array, AIOWPSecurity_User_Login->wp_logout_action_handler

    https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Contributor wpsolutions

    (@wpsolutions)

    We would need more info about your setup.
    Is it single/multi site?

    What was the action you were performing when these errors occurred?

    Can you provide any steps about how we could reproduce this?

    Thread Starter Antipole

    (@antipole)

    Hi… it is multi-site.
    Logging in works, but produces three database errors as below. User name is mg30admin, user number 28.

    thanks for your interest, Tony

    Mar 06, 12:34:00 WordPress database error Table ‘antipole_wp00.wp_12_aiowps_login_activity’ doesn’t exist for query UPDATE wp_12_aiowps_login_activity SET logout_date = ‘2014-03-06 12:34:00’ WHERE user_id = 28 AND login_ip = ‘109.158.111.61’ AND logout_date = ‘0000-00-00 00:00:00’ made by wp_logout, wp_clear_auth_cookie, do_action(‘clear_auth_cookie’), call_user_func_array, AIOWPSecurity_User_Login->wp_logout_action_handler
    Mar 06, 12:34:11 WordPress database error Table ‘antipole_wp00.wp_12_aiowps_login_lockdown’ doesn’t exist for query SELECT * FROM wp_12_aiowps_login_lockdown WHERE release_date > now() AND failed_login_ip LIKE ‘109.158.111%’ made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, wpmem, wpmem_login, wp_signon, wp_authenticate, apply_filters(‘authenticate’), call_user_func_array, AIOWPSecurity_User_Login->aiowp_auth_login, AIOWPSecurity_User_Login->check_locked_user
    Mar 06, 12:34:11 WordPress database error Table ‘antipole_wp00.wp_12_aiowps_login_activity’ doesn’t exist for query INSERT INTO wp_12_aiowps_login_activity (user_id, user_login, login_date, login_ip) VALUES (’28’, ‘mg30admin’, ‘2014-03-06 12:34:11’, ‘109.158.111.61’) made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, wpmem, wpmem_login, wp_signon, do_action(‘wp_login’), call_user_func_array, AIOWPSecurity_User_Login::wp_login_action_handler

    Plugin Contributor wpsolutions

    (@wpsolutions)

    Hi Tony,
    Did you by any chance change the DB prefix for that sub-site using the “DB Prefix” functionality in AIOWPS?

    If you have access to PHPMyAdmin, can you log in and check if the following tables are actually there for this sub-site:
    wp_12_aiowps_login_activity
    wp_12_aiowps_login_lockdown
    wp_12_aiowps_login_activity

    Thread Starter Antipole

    (@antipole)

    No – I have not changed the DB pre-fix – had not plucked up courage for that!

    Have examined DB with PHPMyAdmin and find one set of aiowps tables without the _12 prefix, i.e.:
    wp_aiowps_failed_login
    wp_aiowps_global_meta
    wp_aiowps_login_activity
    wp_aiowps_login_lockdown

    Methinks these tables have been created at the network level but are being sought for at the site level?
    NB I have AIOWPS network activated. Could that be wrong? I might have activated it first at site level – cannot be sure – then decided it would be good to have on all sites so activated at network level.

    thanks, Tony

    Plugin Contributor wpsolutions

    (@wpsolutions)

    No – I have not changed the DB pre-fix – had not plucked up courage for that!

    Ok – I recommend that you don’t change the prefix. We will be making the prefix functionality inaccessible for subsites in the next version of AIOWPS.

    Methinks these tables have been created at the network level but are being sought for at the site level?

    Yes I think you’re right.
    A network activation event will create all of the tables necessary for each subsite. Can you please try deactivating the plugin from the subsite and then trying a network activate.

    Thread Starter Antipole

    (@antipole)

    Could not deactivate at sub-site level as AIOWPS does not show in the list of plugins at sub-site level while it is activated at network level.
    I did a deactivate at network level, and the plugin reappeared at sub site level and as not active. I left that unchanged.
    I then reactivated at network level.
    At sub-site level AIOWPS was available again. I note it had remembered my options from before, so it is not a completely fresh start.
    Problem remains – only tables in DB are without prefix and login/logout activity makes requests with pre-fix

    I await your further advice, Tony

    Plugin Contributor wpsolutions

    (@wpsolutions)

    Ok then please try the following.
    Network deactivate the plugin and then activate it from the subsite you have been referring to.

    Thread Starter Antipole

    (@antipole)

    OK – I deactivated at network level and then activated at site level on several sites.

    The AIOWPS tables have been created with the correct pre-fix (e.g. wp_12_aiowps_login_activity) and the errors have ceased.

    This is a useful work-around. However, as I am sure you will realise, there are some features/settings that are only available at the network level (User Registration for example) and my network level log-in is not protected from a Brute Force attack.

    Thank you for your help and support.

    regards, Tony

    Plugin Contributor wpsolutions

    (@wpsolutions)

    Thanks for the confirmation Tony.

    We will check our code to see why the network activation event is not creating subsite tables and fix if necessary.

    Hiya,

    Just wanted to note that I also get this issue and activating on each individual site remedied the issue (note that Multisite Plugin Manager is useful there).

    I didn’t see anything in the changelog for v3.7.3 that eluded to a fix so didn’t go so far as to upgrade, but if the fix is there it’d be useful to know.

    Thanks!

    Plugin Contributor wpsolutions

    (@wpsolutions)

    Ok thanks for the clarification.
    No there was no fix for this issue in the last release.
    We will try and resolve this for the next release.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Database errors’ is closed to new replies.