E_ERROR when updating to 3.5.2

  • Resolved kaj69

    (@kaj69)


    5 years ago

    Hi,
    After updating the free version of WPSAL to v3.5.2 then we get an error message when accessing the admin page:

    An error of type E_ERROR occured at line 98 in following file:

    /<the path to website>/wp-content/plugins/wp-security-audit-log/classes/Update/Task/CronNameRemap.php. Reason: Uncaught Error: Call to a member function GetArchivingRunEvery() on null in /<the path to website>/wp-content/plugins/wp-security-audit-log/classes/Update/Task/CronNameRemap.php:98
    Stack trace:
    #0 /<the path to website>/wp-content/plugins/wp-security-audit-log/classes/Update/Task/CronNameRemap.php(45): WSAL\Update\Task\CronNameRemap->get_crons_to_remap()
    #1 /<the path to website>/wp-content/plugins/wp-security-audit-log/wp-security-audit-log.php(1463): WSAL\Update\Task\CronNameRemap->run()
    #2 /<the path to website>/wp-includes/class-wp-hook.php(288): WpSecurityAuditLog->{closure}(”)
    #3 /<the path to website>/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(NULL, Array)
    #4 /<the path to website>/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #5 /<the path to website>/wp-settings.php(523): do_action(‘init’)
    #6 /<the path to website>/wp-config.php(90): require_once(‘/home/reinscom/…’)
    #7 /<the path to website>/w

    However, if logging out and in again the message is not shown.

    Is it an “once-time” error due to the update or is it a more serious error?
    Will this also occur when updating the paid version?

    Kaj

Viewing 8 replies - 1 through 8 (of 8 total)
  • asnowstorm

    (@asnowstorm)

    I also just got an error notification email from WordPress when I updated to 3.5.2, although it didn’t specify what type of error, it just gave me a link to a page that has the error. When I check that link, I just see 0 in the top left corner of the page. I just did a rollback to the previous plugin version, but that link now looks the same as with 3.5.2.
    I do have the link, but prefer to send that my personal message to someone who might be able to shine any light on the issue, for security reasons.
    Many thanks for any thoughts!
    Anna

    • This reply was modified 5 years ago by asnowstorm.
    Plugin Support robertabela

    (@robert681)

    Hello @kaj69 and @asnowstorm

    Sorry to hear you are encountering such an error. This is a one time error because it is generated by an update script we developed to standardize the names of the plugin’s cron jobs. So for now you have nothing to worry about.

    However, I have a question which can help us solve this issue in future updates: can you please tell me what are the retention settings of your activity logs? Do you keep all logs, or is the plugin configured to purge data that is older than X months or years, or archive it?

    Looking forward to hearing from you and sorry if this error has caused any inconvenience.

    asnowstorm

    (@asnowstorm)

    Mine’s set to purge everything that’s 6 months old (I think this was a default setting).
    I’ll update again to the new version then, if the error is nothing to worry about.
    Many thanks for your quick reply!

    Thread Starter kaj69

    (@kaj69)

    Same here, to delete entries older than 6 months.

    Thanks for your rapid reply – this is what I call “High Quality Service”!

    Plugin Support robertabela

    (@robert681)

    Can please confirm the version of the plugin from which you were updating @kaj69 and @asnowstorm ?

    Thread Starter kaj69

    (@kaj69)

    From v3.5.1.1 to v3.5.2 on WP v5.3

    Plugin Support robertabela

    (@robert681)

    Finally we managed to reproduce the issue @kaj69 and @asnowstorm

    Thank you very much for all the details. We are working on a hot fix and should release it within the next few hours.

    Plugin Support robertabela

    (@robert681)

    Hello @kaj69 and @asnowstorm

    We have just released update 3.5.2.1 which addresses this problem. Thank you for reporting it and sorry if this has caused any inconvenience.

    Should you have any other queries please do not hesitate to get in touch. Thank you for using our plugin.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘E_ERROR when updating to 3.5.2’ is closed to new replies.