Replies: 0
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 1332Is 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.