Fatal error

  • Resolved Jennifer

    (@akpae5)


    1 year, 3 months ago

    hello, dear developers thank you for building a fantastic plugin which we all benefits from it in most cases we may have some issues about a specific plugin and it definitely accelerated the issues that I had is that after I upgraded to version 5.2.2 if I wanted to activate the plugin it will say (Fatal error) please I need help with this your assistance will highly appreciate. Fatal error: Uncaught Error: Call to a member function set_value() on null in /home/submitmo/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-configure-settings.php:267 Stack trace: #0 /home/submitmo/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-installer.php(38): AIOWPSecurity_Configure_Settings::add_option_values() #1 /home/submitmo/public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/wp-security-core.php(269): AIOWPSecurity_Installer::run_installer('') #2 /home/su

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @akpae5

    I will create internal ticket for this, It seems firewall config file did not loaded some how.

    Do you have this site copied from some where else ?

    Regards

    Thread Starter Jennifer

    (@akpae5)

    Hi, thanks for your response, No I don’t have a copied of this site some where else.

    Plugin Support aporter

    (@aporter)

    Hi,

    We haven’t been able to reproduce this issue and we have only had one other report.

    Would you be able to provide some more information:

    1) how did you update the plugin (did you use a plugin, cli, the gui, etc..)

    2) if the firewall is setup or not

    3) php version and web server information

    Best Wishes,

    Ashley

    From one day to the next, suddenly unusable right after the last update. Had to be deleted.

    Fatal error: Uncaught Error: Call to a member function set_value() on null in /homepages/32/d71397779/htdocs/clickandbuilds/FSTeV/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-configure-settings.php:267 Stack trace: #0 /homepages/32/d71397779/htdocs/clickandbuilds/FSTeV/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-installer.php(38): AIOWPSecurity_Configure_Settings::add_option_values() #1 /homepages/32/d71397779/htdocs/clickandbuilds/FSTeV/wp-content/plugins/all-in-one-wp-security-and-firewall/wp-security-core.php(269): AIOWPSecurity_Installer::run_installer() #2 /homepages/32/d71397779/htdocs/clickandbuilds/FSTeV/wp-includes/class-wp-hook.php(310): AIO_WP_Security::activate_handler() #3 /homepages/32/d71397779/htdocs/clickandbuilds/FSTeV/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters() #4 /homepages/32/d71397779/htdocs/clickandbuilds/FSTeV/wp-includes/plugin.php(517): WP_Hook->do_action() #5 /homepages/32/d71397779/htdocs/clickandbuilds/FSTeV/wp-admin/plugins.php(194): do_action() #6 {main} thrown in?/homepages/32/d71397779/htdocs/clickandbuilds/FSTeV/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-configure-settings.php?on line?267

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @bytes4fun

    It seems issue regarding the “wp-content/uploads/aios/firewall-rules” folder do not exits. we have tracked down the issue and a copy of the plugin with the fix is here:

    https://gofile.io/d/FMt8GE

    If the above copy does resolve the issue for you then for some reason on the two sites where it doesn’t work the “wp-content/uploads/aios/firewall-rules” folders did not exist in your uploads directory and that causes the firewall to fail to load.

    Let me know if still any other issue.

    Regards

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @akpae5 @bytes4fun

    As per the recent AIOS release, this issue should be solved now.

    Please update to AIOS 5.2.4 Let us know if still an issue.

    Regards

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Fatal error’ is closed to new replies.