Conversation
supportIn wordpress 6.8.1, installing this plugin causes a critical error. The plugin need then need to be deactivaded through ftp to be able to access the site. This has happened on several sites (but not on all). Below is the error log. Any idea if this can be solved? Error Details ============= An error of type E_ERROR was caused in line 450 of the file /home/ hannekevaneijken.nl/public_html/wp-content/plugins/advanced-access-manager/application/Framework/Manager.php . Error message: Uncaught Error: Call to a member function list() on null in /home/ hannekevaneijken.nl/public_html/wp-content/plugins/advanced-access-manager/application/Framework/Manager.php:450 Stack trace: #0 /home/ hannekevaneijken.nl/public_html/wp-content/plugins/advanced-access-manager/application/Framework/Manager.php (431): AAM_Framework_Manager->_update_user_capabilities() #1 /home/ hannekevaneijken.nl/public_html/wp-content/plugins/advanced-access-manager/application/Framework/Manager.php (241): AAM_Framework_Manager->_dynamically_adjust_user_account() #2 /home/ hannekevaneijken.nl/public_html/wp-includes/class-wp-hook.php (324): AAM_Framework_Manager->{closure}() #3 /home/ hannekevaneijken.nl/public_html/wp-includes/class-wp-hook.php (348): WP_Hook->apply_filters() #4 /home/ hannekevaneijken.nl/public_html/wp-includes/plugin.php (517): WP_Hook->do_action() #5 /home/ hannekevaneijken.nl/public_html/wp-includes/pluggable.php (48): do_action() #6 /home/ hannekevaneijken.nl/public_html/wp-includes/user.php (3759): wp_set_current_user() #7 /home/ hannekevaneijken.nl/public_html/wp-includes/pluggable.php (70): _wp_get_current_user() #8 /home/ hannekevaneijken.nl/public_html/wp-includes/l10n.php (98): wp_get_current_user() #9 /home/ hannekevaneijken.nl/public_html/wp-includes/l10n.php (153): get_user_locale() #10 /home/ hannekevaneijken.nl/public_html/wp-includes/l10n.php (1364): determine_locale() #11 /home/ hannekevaneijken.nl/public_html/wp-includes/l10n.php (1409): _load_textdomain_just_in_time() #12 /home/ hannekevaneijken.nl/public_html/wp-includes/l10n.php (195): get_translations_for_domain() #13 /home/ hannekevaneijken.nl/public_html/wp-includes/l10n.php (307): translate() #14 /home/ hannekevaneijken.nl/public_html/wp-content/plugins/updraftplus/updraftplus.php (122): __() #15 /home/ hannekevaneijken.nl/public_html/wp-content/plugins/updraftplus/updraftplus.php (171): updraftplus_list_cron_schedules() #16 /home/ hannekevaneijken.nl/public_html/wp-includes/class-wp-hook.php (324): updraftplus_modify_cron_schedules() #17 /home/ hannekevaneijken.nl/public_html/wp-includes/plugin.php (205): WP_Hook->apply_filters() #18 /home/ hannekevaneijken.nl/public_html/wp-includes/cron.php (1136): apply_filters() #19 /home/ hannekevaneijken.nl/public_html/wp-includes/cron.php (247): wp_get_schedules() #20 /home/ hannekevaneijken.nl/public_html/wp-content/plugins/advanced-access-manager/application/Service/SecurityAudit.php (69): wp_schedule_event() #21 /home/ hannekevaneijken.nl/public_html/wp-content/plugins/advanced-access-manager/application/Service/BaseTrait.php (42): AAM_Service_SecurityAudit->__construct() #22 /home/ hannekevaneijken.nl/public_html/wp-content/plugins/advanced-access-manager/aam.php (156): AAM_Service_SecurityAudit::bootstrap() #23 /home/ hannekevaneijken.nl/public_html/wp-includes/class-wp-hook.php (324): AAM::on_plugins_loaded() #24 /home/ hannekevaneijken.nl/public_html/wp-includes/class-wp-hook.php (348): WP_Hook->apply_filters() #25 /home/ hannekevaneijken.nl/public_html/wp-includes/plugin.php (517): WP_Hook->do_action() #26 /home/ hannekevaneijken.nl/public_html/wp-settings.php (578): do_action() #27 /home/ hannekevaneijken.nl/public_html/wp-config.php (105): require_once('...') #28 /home/ hannekevaneijken.nl/public_html/wp-load.php (50): require_once('...') #29 /home/ hannekevaneijken.nl/public_html/wp-admin/admin.php (35): require_once('...') #30 {main} thrown This topic was modified 1 year ago by raoulunger . This topic was modified 1 year ago by raoulunger .
@raoulunger thank you for the report. That is an interesting issue and following the trace it is also impossible for this error to occur. I’m wondering if you may have a corrupted AAM installation. Please try to delete the advanced-access-manager folder and reinstall it again from the official WP.org repository. It is possible that not all files got replaced during upgrade.
Hi, actually it was a first install (on a new site) directly from within WordPress (so from the official WP-repository.) The moment I ‘activate’ the plugin, the site crashes, and gives the critical error. I changed the plugin’s folder name, after which I could again get back into WP. I then removed the plugin. Then I downloaded an older version (6) and installed that. That works fine. But the moment I update to the latest version, the sites crashes again. I’m now back to version 6.
Hm, interesting. Ok. I’m wondering if there is some sort of conflict. I see the trace goes through “updraftplus” plugin. I’ll try to install and replicate an issue.
@raoulunger got it. Identified the root cause. We are going to adjust AAM functionality in the next minor release 7.0.2 to work better with plugins that hook into WP core initialization early on.
OK, that’s good news – I’ll wait for 7.0.2 then! Thanks for the prompt follow up.
Hi. I’m having this problem too with the latest update of AAM. Is there an ETA on version 7.0.2? Thanks.
Hi, it’s already there! I updated to 7.0.2 last Thursday, and everything works fine now (at my side at least). Cheers
Well, I see now that I already have version 7.0.2 and still having problems. For example, when this plugin is activated and I go into the menu management, I get an error that WordPress has now technical issues. I also get the automated email from the site, indicating that this plugin is the cause for the issues. I should mention though that when having this issue, the site itself (frontend) is working fine, and other admin functions are not affected, as far as I can see. When I deactivate AAM, the menus admin page is working fine. Also, I have a few sites that are pretty similar in their installed plugins, and all are with WooCommerce in this case, and none of the other sites with AAM (latest version have the issue with menus admin page). I’m trying to figure out what is different about this site that AAM causes this issue in it…
I think there is already a thread about that new error: https://wordpress.org/support/topic/v-7-0-2-crash-the-wp-admin-apparence-menu/
@raoulunger thank you for the report. That is an interesting issue and following the trace it is also impossible for this error to occur. I’m wondering if you may have a corrupted AAM installation. Please try to delete the advanced-access-manager folder and reinstall it again from the official WP.org repository. It is possible that not all files got replaced during upgrade.
Hi, actually it was a first install (on a new site) directly from within WordPress (so from the official WP-repository.) The moment I ‘activate’ the plugin, the site crashes, and gives the critical error. I changed the plugin’s folder name, after which I could again get back into WP. I then removed the plugin. Then I downloaded an older version (6) and installed that. That works fine. But the moment I update to the latest version, the sites crashes again. I’m now back to version 6.
Hm, interesting. Ok. I’m wondering if there is some sort of conflict. I see the trace goes through “updraftplus” plugin. I’ll try to install and replicate an issue.
@raoulunger got it. Identified the root cause. We are going to adjust AAM functionality in the next minor release 7.0.2 to work better with plugins that hook into WP core initialization early on.
OK, that’s good news – I’ll wait for 7.0.2 then! Thanks for the prompt follow up.
Hi. I’m having this problem too with the latest update of AAM. Is there an ETA on version 7.0.2? Thanks.
Hi, it’s already there! I updated to 7.0.2 last Thursday, and everything works fine now (at my side at least). Cheers
Well, I see now that I already have version 7.0.2 and still having problems. For example, when this plugin is activated and I go into the menu management, I get an error that WordPress has now technical issues. I also get the automated email from the site, indicating that this plugin is the cause for the issues. I should mention though that when having this issue, the site itself (frontend) is working fine, and other admin functions are not affected, as far as I can see. When I deactivate AAM, the menus admin page is working fine. Also, I have a few sites that are pretty similar in their installed plugins, and all are with WooCommerce in this case, and none of the other sites with AAM (latest version have the issue with menus admin page). I’m trying to figure out what is different about this site that AAM causes this issue in it…
I think there is already a thread about that new error: https://wordpress.org/support/topic/v-7-0-2-crash-the-wp-admin-apparence-menu/