• Resolved sonofseagull

    (@sonofseagull)


    After plugin updates today on one of the customer sites we support we got this error, and now we can’t run wordfence at all, not the old version, not the new version (7.4.0) on that site. No surrounding code has been changed,
    Tried full uninstall and reinstall, tried deactivating all other plugins, nothing helps.

    Tried it on PHP7.2 (customers server is locked to that), 7.4, 8.0 with WP6.1
    Same result.

    Grateful for any help on this.
    /Dan

    
    Fatal error: wfWAFWordPress::runCron(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "wfWAFCronFetchCookieRedactionPatternsEvent" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide an autoloader to load the class definition in /kunder/xxxxxx/xxxxxx/public/wp-content/plugins/wordfence/waf/bootstrap.php on line 474
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @sonofseagull, thanks for getting in touch.

    I’ve not seen this failure before first-hand, but there was one previous mention that I managed to find. I’d recommend stopping any scan (if it’s running), then remove the wp-content/wflogs/config-livewaf.php file and update the plugin. If you still have the same issue, remove the new config-livewaf.php once more to let it be regenerated by the new plugin version.

    If that doesn’t seem to help, please drop us a diagnostic report to wftest @ wordfence . com using the link at the top of the Wordfence > Tools > Diagnostics page, I can look into this further for you. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,
    Peter.

    Thread Starter sonofseagull

    (@sonofseagull)

    Thank you for the tips.
    We’ll give it a try 🙂

    Plugin Support wfpeter

    (@wfpeter)

    Hi @sonofseagull, how did you get on?

    Thread Starter sonofseagull

    (@sonofseagull)

    Ouch forgot to answer, Sorry.
    We ended up backing out of all plugin updates to an older commit, and then updated wordfence first, then the rest one at a time, and then it worked.
    Really odd, appreciated your tips and suggestions.
    /Dan

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

The topic ‘Fatal error: wfWAFWordPress::runCron():’ is closed to new replies.