Multisite errors after 5.2.7 Upgrade

  • Resolved Rhapsody348

    (@rhapsody348)


    1 year, 1 month ago

    The following errors are generated after upgrading to 5.2.7:

    [09-Feb-2024 06:23:01 America/New_York] PHP Warning:  Undefined array key "SCRIPT_FILENAME" in /..../wp-content/plugins/all-in-one-wp-security-and-firewall/classes/firewall/rule/rules/general/rule-proxy-comment-posting.php on line 42

    The following happens on multiple sites and multiple IP addresses:

    [09-Feb-2024 10:29:44 UTC] WordPress database error Unknown column 'released' in 'where clause' for query SELECT * FROM wp_72_aiowps_login_lockdown WHERE released > UNIX_TIMESTAMP() AND failed_login_ip = '136.243.220.209' 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_user
    [09-Feb-2024 11:30:41 UTC] WordPress database error Unknown column 'created' in 'where clause' for query DELETE FROM wp_76_aiowps_events WHERE created < '1699702241' made by do_action_ref_array('aiowps_daily_cron_event'), WP_Hook->do_action, WP_Hook->apply_filters, AIOWPSecurity_Cronjob_Handler->aiowps_daily_cron_event_handler, do_action('aiowps_perform_db_cleanup_tasks'), WP_Hook->do_action, WP_Hook->apply_filters, AIOWPSecurity_Cleanup->aiowps_scheduled_db_cleanup_handler, AIOWPSecurity_Utility::purge_table_records
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Rhapsody348

    (@rhapsody348)

    The first error is being generated during a cron job so the $_SERVER variables do not exist. I made the following patch to correct the problem until it is fixed in the next update. This is done by testing for isset($_SERVER[‘SCRIPT_FILENAME’]) on rule-proxy-comment-posting.php line 42

    //Preconditions for the rule
$is_comment_form = (isset($_SERVER['SCRIPT_FILENAME']) && 1 === preg_match('/\/wp-comments-post\.php$/i', $_SERVER['SCRIPT_FILENAME']));
    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @rhapsody348,

    Ok, I will create internal ticket for the check so cronjob do not have warning. isset($_SERVER['SCRIPT_FILENAME']) and will be in next release.

    for database errors it might be some how the newly added released column is not there in DB, If possible try access admin panel of the site it will apply the plugin DB changes as per new version.

    If still that issue let us know.

    Regards

    Thread Starter Rhapsody348

    (@rhapsody348)

    @hjogiupdraftplus – I checked using phpmyadmin and the released column is missing in the wp_xx_aiowps_login_lockdown tables from a number of sites. I accessed the WP Security dashboard for sites that are showing in the error log and can confirm that this created the missing fields.

    The multisite application I run has over 100 sites so doing this manually is tedious. My suggested fix is that for multisite that the plugin be updated so when the master site dashboard is opened, all sites are scanned for the proper database table structure and if needed any fields detected as missing or not modified per the latest plugin update be flagged. Should the scan find a table flagged, it would call a routine to properly change the database structure.

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @rhapsody348,

    Ok, I will create an internal ticket for this. “so the master site dashboard is opened, all sites are database table structure changes applied as per new version”

    Regards

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Multisite errors after 5.2.7 Upgrade’ is closed to new replies.