• Resolved tymonello

    (@tymonello)


    I have just updated WordPress from 6.4.4 to 6.5.2 and All In One WP Security to 5.2.9.

    After going to Captcha settings in Brute Force (wp-admin/admin.php?page=aiowpsec_brute_force&tab=captcha-settings) I received an information that a critical error happened.

    If you want I can send to you a full stacktrace via email, I don’t know if posting it here would be a security issue or not, but basically the error is: “Uncaught Error: Call to a member function get_supported_captchas() on null

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

    (@hjogiupdraftplus)

    Hi @tymonello

    We have AIOS 5.2.9 on ?6.5.2 working fine and do not have general issue

    Call to a member function get_supported_captchas() on null

    It is due to the $aio_wp_security->captcha_obj which is assinged the new AIOWPSecurity_Captcha(); object is null it may be due to the related file corrupted or any other issue.

    Can you please upload again the downloaded zip file of AIOS 5.2.9 plugin and Add New Plugin,

    and replace existing with uploaded it will update all files again and then please corss check.

    Do you have the contact form 7 plugin installed make sure it is up to date.

    You may share the stack trace using https://pastebin.com/ burn after read option.

    Regards

    Thread Starter tymonello

    (@tymonello)

    Hello, thank you for your reply.

    I have uninstalled the plugin and installed it again via the wp-admin/plugin-install.php page. I don;t have Contact Form 7 plugin installed. I only have WPForms Lite.
    Here is the full stack trace:
    https://pastebin.com/HqLDRv6N
    and the password is “aios”

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @tymonello,

    Uninstalled the AIOS plugin and installed it again, Has it solved the issue?

    The stack trace just shows it tries to access the Bruteforce > Captcha settings tab page at that time the issue is.

    Regards?

    Thread Starter tymonello

    (@tymonello)

    No, reinstalling the plugin did not help. I am running some websites with this plugin as well, so I checked a differnet website, running 5.2.9 of AIOS and WordPress has not been yet updated, so it is on version 6.4.4 and there the same issue happens. The error and stack traces are identical.

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @tymonello

    If I corss check here for AIOS 5.2.9 and WordPress 6.5.2, The page loads fine. As it is the first time such an issue reported by someone, I will create internal ticket for this.

    Can you please try disabling Plugins one by one from the Plugins list and cross-check if there is a conflict due to any other plugin? Also please let me know the theme you use.

    Regards

    Thread Starter tymonello

    (@tymonello)

    Yes, I can do that, I will start disabling all plugins I have one by one to see if the issue will be resolved.

    Thread Starter tymonello

    (@tymonello)

    I checked that and the issue went away when Shield Security (v19.1.6) has been disabled.

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @tymonello,

    Thanks for the identifying the conflict with the Shield Security (v19.1.6)?Plugin,

    We will cross check it in details and if fix from our side required will work on that. I will keep you updated.

    Regards

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @tymonello

    The problem is the?Shield Security?plugin removes our plugin init code wp_security_plugin_init . Can you please contact Shield Security support for this issue?

    It is advisable to use only one Security-related plugin instead of two.

    /wp-content/plugins/wp-simple-firewall/src/lib/src/Modules/Plugin/Processor.php includes these lines;

     protected function removePluginConflicts() {
            if ( \class_exists( 'AIO_WP_Security' ) && isset( $GLOBALS[ 'aio_wp_security' ] ) ) {
                remove_action( 'init', [ $GLOBALS[ 'aio_wp_security' ], 'wp_security_plugin_init' ], 0 );
            }
Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Error after Update’ is closed to new replies.