Errors with 7.11

  • Resolved johnrhopkins

    (@johnrhopkins)


    6 years, 8 months ago

    Hello, it appears that the update to 7.11 caused us to get the white screen of death.

    With debug mode turned on, I get:
    Warning: require_once(/home/virtutraining/public_html/members/wp-content/plugins/wordfence/waf/../vendor/wordfence/wf-waf/src/init.php): failed to open stream: No such file or directory in /home/virtutraining/public_html/members/wp-content/plugins/wordfence/waf/bootstrap.php on line 13

    Fatal error: require_once(): Failed opening required ‘/home/virtutraining/public_html/members/wp-content/plugins/wordfence/waf/../vendor/wordfence/wf-waf/src/init.php’ (include_path=’.:/opt/alt/php70/usr/share/pear’) in /home/virtutraining/public_html/members/wp-content/plugins/wordfence/waf/bootstrap.php on line 13

    When I disable the plugin by changing the plugin folder name I get the following error when trying to re-enable it:

    Plugin could not be activated because it triggered a fatal error.

    Warning: require_once(vendor/wordfence/wf-waf/src/init.php): failed to open stream: No such file or directory in /home/virtutraining/public_html/members/wp-content/plugins/wordfencex/wordfence.php on line 52

    The page I need help with: [log in to see the link]

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

  • Might be specific to your site or site config, as all my client sites (20+) upgraded automatically without difficulty.

    No problem with upgrades here so far, liking the Block Table sorting, what a concept! MTN

    Just to assure you you are not going mad, OP. I have had a couple of issues this morning with WordFence and HTTP 500 errors which, when I disabled the plugin via FTP, went away. Obviously there is some sort of conflict.

    I updated other plugins and attempted to update WordFence (which obviously failed as the plugin could not be found). Then, when I renamed the plugin folder back to “wordfence” it appeared to be working again. I’m not smart enough to know what was going on, but it does appear to be WordFence related (or WordFence conflicting with something).

    Hi johnrhopkins!
    The errors you shared indicate you have a corrupt plugin update. For some reason your plugin ended up with missing files. This could be due to connectivity issues during the update, lack of disk space on the server, or possibly temporary hardware failure.

    To fix it simply use FTP/SSH or any file browser your web host may be providing to access your site, remove the wordfence folder located in wp-content/plugins and reinstall Wordfence from the WordPress plugins page.

    Thread Starter johnrhopkins

    (@johnrhopkins)

    Thanks @wfasa, that is pretty much what I did. I uninstalled it in the wordpress interface and reinstalled it the same way. Back up and running.

    Okay great! If it happens more times I suggest you reach out again. If so, mention that it’s happened several times and we’ll try to dig a bit deeper.

    Best of luck for now!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Errors with 7.11’ is closed to new replies.