“fopen” error on a debug after a crash

  • Resolved David Borrink

    (@davidborrink)


    3 years, 6 months ago

    Doing a routine plug-in update after a backup resulted in a site crash. The hosting company thinks that Wordfence might have caused it. Here are the error messages on the site in debug mode…

    Warning: fopen(/home/bellem9/bellemorepiperelining.com/wp-content/plugins/wordfence/waf/../languages/wordfence.mo): failed to open stream: No such file or directory in /home/bellem9/bellemorepiperelining.com/wp-content/plugins/wordfence/waf/pomo/streams.php on line 185

Warning: Cannot modify header information - headers already sent by (output started at /home/bellem9/bellemorepiperelining.com/wp-content/plugins/wordfence/waf/pomo/streams.php:185) in /home/bellem9/bellemorepiperelining.com/wp-includes/pluggable.php on line 1329

Warning: Cannot modify header information - headers already sent by (output started at /home/bellem9/bellemorepiperelining.com/wp-content/plugins/wordfence/waf/pomo/streams.php:185) in /home/bellem9/bellemorepiperelining.com/wp-includes/pluggable.php on line 1332

    Is there anything I could do, like a database edit to solve this? I already renamed the plug-in folder “x-wordfence” to deactivate it. I’d like to avoid doing a fresh install of WordPress and a restore using Updraftplus if it’s possible to fix a couple existing things.

Viewing 1 replies (of 1 total)
  • Thread Starter David Borrink

    (@davidborrink)

    We solved it by deleting our WordPress install after doing a server backup. The new install was created by using the same database name. It somehow grabbed onto the old database and had the site in recovery mode. We deleted Wordfence and that removed the error message. We then ran Updraftplus to grab a backup from two days ago and that got things back to where they were.

    Then we ran updaters again and this time no glitch. Apparently we just had a flukey update process that hiccuped.

Viewing 1 replies (of 1 total)
  • The topic ‘“fopen” error on a debug after a crash’ is closed to new replies.

Tags