• Resolved CarstenTimm

    (@carstentimm)


    From the email sent when the error was thrown:

    WordPress-version 6.6.2
    Nuv?rende plugin: Really Simple Security (version 9.0.2)
    PHP version 8.1.30 Detaljer om fejl

    En fejl af typen E_ERROR skete i linje 2532 i filen //public/wp-content/plugins/really-simple-ssl/class-admin.php. Fejlbesked: Uncaught Error: Value of type bool is not callable in //public/wp-content/plugins/really-simple-ssl/class-admin.php:2532
    Stack trace: 0 //public/wp-content/plugins/really-simple-ssl/class-admin.php(2351): rsssl_admin->validate_function() 1 //public/wp-content/plugins/really-simple-ssl/class-admin.php(2569): rsssl_admin->get_notices_list() 2 //public/wp-content/plugins/really-simple-ssl/settings/settings.php(173): rsssl_admin->count_plusones() 3 //public/wp-includes/class-wp-hook.php(324): rsssl_add_top_level_menu() 4 //public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 5 //public/wp-includes/plugin.php(517): WP_Hook->do_action() 6 //public/wp-admin/includes/menu.php(161): do_action() 7 //public/wp-admin/menu.php(412): require_once(‘…’) 8 //public/wp-admin/admin.php(158): require(‘…’) 9 //public/wp-admin/index.php(10): require_once(‘…’) 10 {main}

    thrown

    One final thing, I updated the collation in the database prior to this thing happening, I tested it a while back on a staging environment, with an older version of Really Simple Security, and it worked, so not sure if that is to blame at all…

    Please advice what to do?

    For now I will try to disable the plugin by renaming the folder using FTP, and hoping for a response from you ??

    All the best
    Carsten

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter CarstenTimm

    (@carstentimm)

    After renaming the folder for the Really simple security and the pro version, I can now login to the backend, no problem.

    If I just want to remove the two plugins, is there anything I need to be aware of?

    All the best
    Carsten

    Plugin Support jarnovos

    (@jarnovos)

    Hi @carstentimm,

    After I read your message more closely, it sounds like you might’ve had the Free and Pro plugin activated next to each other. Was this the case for you? If so, that might’ve caused this issue.

    I would be interested to know whether the issue is fixed by only having the latest Pro plugin active on your site; and no other versions (e.g., Free) enabled next to it. Could you verify this?

    As for your last addition: If you’ve already disabled the plugin(s) and everything still works, then you can indeed safely delete the plugins.

    Kind regards, Jarno

    • This reply was modified 1 month, 2 weeks ago by jarnovos.
    Thread Starter CarstenTimm

    (@carstentimm)

    Hi @jarnovos

    The collation algorithm has been updated to utf8mb4_unicode_520_ci across all tables in the database, to avoid mix of collation errors.
    It worked without any problems on the staging site, and that site still runs without issues, so a little strange if that is the cause of the problem.

    Let me know if I should try anything else?

    Kind regards
    Carsten

    Plugin Support jarnovos

    (@jarnovos)

    Hi @carstentimm,

    I updated my above response after I read that you seemed to have two versions of the plugin (Free + Pro) activated at the same time.

    Could you try the updated suggestion above: delete both versions of the plugin from your site to start from a clean slate; and then re-install & activate only the latest Pro plugin?

    Kind regards, Jarno

    Thread Starter CarstenTimm

    (@carstentimm)

    Hi again @jarnovos

    Yes I had both the Free and Pro plugin activated next to each other. And I am a little concerned that deactivating the pro, will cause problems with some of the security headers, but I’m not sure about that.

    It was an older version of the Pro and the newest version of the free plugin

    Again let me know if I should try anything to help you debug, and to help get it working again ??

    Kind regards
    Carsten

    Plugin Support jarnovos

    (@jarnovos)

    Hi @carstentimm,

    If you use the Pro plugin, you shouldn’t have the Free plugin enabled next to it.

    This is almost certainly the cause of the issue, having Free & Pro enabled next to each other and also with differing versions between the two.

    You can remove the Free plugin (select “Keep HTTPS” if you’re prompted to), then update Pro to the latest available version, and check if the issue is resolved now that you only have one version of the plugin enabled; the latest version.

    Kind regards, Jarno

    Thread Starter CarstenTimm

    (@carstentimm)

    I bought a new licens for the pro version of the plugin

    First I renamed the folders back to their original name, then I first reactivated the free plugin, then deactivated it and deleted it, I then updated the pro plugin by uploading the new version, and replaced the old version of the pro plugin.

    The site woks, and I have the newest version of the pro plugin now.

    I think that updating the collation algorithm was just a coincidence, well the site works now, and that is the most important!

    Question:
    Will the settings from the old pro version still be there, or do I need to reapply them by going through the setup again?

    I will explore the new updated pro version, and see what that offers of new goodies ??

    Kind regards
    Carsten

    Plugin Support jarnovos

    (@jarnovos)

    Hi @carstentimm,

    Glad to hear, and I agree with your assessment that the collation change was likely unrelated to this behavior.

    While the settings from the previous Pro version should persist, we would definitely recommend browsing through the options once more to verify if this is the case; and as you updated from an earlier version of the plugin, there will be new functionality available to you as well :).

    I’ll mark this thread as resolved for now.

    Kind regards, Jarno

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