Critical Error on plugin upgrade

  • Resolved ignitionmedia

    (@ignitionmedia)


    2 months, 2 weeks ago

    I just tried to upgrade and it caused a critical error. I’ve had to uninstall the plugin but I need it. Any ideas?

    Warning: Invalid argument supplied for foreach() in /home/vqabnz80ri5d/public_html/melprivapts/wp-content/plugins/advanced-access-manager/application/Migration/Migration_6_9_36.php on line 29

    Fatal error: Uncaught TypeError: Argument 1 passed to AAM_Framework_Service_Settings::set_settings() must be of the type array, bool given, called in /home/vqabnz80ri5d/public_html/melprivapts/wp-content/plugins/advanced-access-manager/application/Migration/Migration_6_9_36.php on line 41 and defined in /home/vqabnz80ri5d/public_html/melprivapts/wp-content/plugins/advanced-access-manager/application/Framework/Service/Settings.php:83 Stack trace: #0 /home/vqabnz80ri5d/public_html/melprivapts/wp-content/plugins/advanced-access-manager/application/Migration/Migration_6_9_36.php(41): AAM_Framework_Service_Settings->set_settings(false) #1 /home/vqabnz80ri5d/public_html/melprivapts/wp-content/plugins/advanced-access-manager/application/Migration/Migration_6_9_36.php(92): AAM_Migration_6_9_36->run() #2 /home/vqabnz80ri5d/public_html/melprivapts/wp-content/plugins/advanced-access-manager/application/Core/Migration.php(158): include(‘/home/vqabnz80r…’) #3 /home/vqabnz80ri5d/public_html/melprivapts/wp-content/plugins/advanced-acc in /home/vqabnz80ri5d/public_html/melprivapts/wp-content/plugins/advanced-access-manager/application/Framework/Service/Settings.php on line 83
    There has been a critical error on this website. Please check your site admin email inbox for instructions.

Viewing 4 replies - 1 through 4 (of 4 total)

  • We are getting this same issue after upgrading today.

    Plugin Author AAM Plugin

    (@vasyltech)

    Hello @sagescrub. We worked with @ignitionmedia offline to understand the root cause and found that the root cause is in the fact that one of the database option aam_access_settings, AAM uses to store access controls was corrupted. Based on the type of corruption, it appears that the raw value was manually modified in database directly.

    You have two options here:

    • You can send us ([email protected]) the export of your wp_options database table to us. We need only values that start with aam_ prefix. This way we can help to identify the corruption and instruct how to fix it.
    • You can manually delete the aam_access_settings option from the DB and this will solve the problem.

    @vasyltech thank you so much! I did the manual deletion and that seems to have fixed it!!

    Hello!

    In version 6.9.41 the backend works fine again now.
    Thank you!

    Kind regards,
    Gerald

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.