Post 7.4.4. update fatal error

  • Resolved alexanderharmsen

    (@alexanderharmsen)


    6 years, 4 months ago

    Wordfence all good many years. Now update 7.4.4 causing fatal error. Have deactivated Wordfence. Are you aware of post update issues?

    Plugin could not be activated because it triggered a fatal error.
    Warning: require_once(/var/www/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/init.php): failed to open stream: No such file or directory in /var/www/wp-content/plugins/wordfence/wordfence.php on line 66

    Fatal error: require_once(): Failed opening required ‘/var/www/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/init.php’ (include_path=’.:/opt/remi/php72/root/usr/share/pear:/opt/remi/php72/root/usr/share/php:/usr/share/pear:/usr/share/php’) in /var/www/wp-content/plugins/wordfence/wordfence.php on line 66

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • wfdave

    (@wfdave)

    6 years, 4 months ago

    Hi @alexanderharmsen,

    This seems to be caused by an interrupted update. Files are deleted, but not replaced during the update, as shown by the error No such file.

    Can you reinstall Wordfence and see if that causes the error to go away?

    In the past, we’ve had users with the same issue and this has been caused by LiteSpeed terminating the Wordfence process during an update. If that’s the case for you, there’s an article here to help you prevent these types of issues in the future.

    https://www.wordfence.com/help/advanced/system-requirements/litespeed/

    Dave

    WFGerroald

    (@wfgerald)

    6 years, 3 months ago

    Hi @alexanderharmsen,

    We haven’t heard back from you in a while, so I’ve gone ahead and marked this thread as resolved.

    Please feel free to open another thread if you’re still having issues with Wordfence.

    Thanks,

    Gerroald

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

The topic ‘Post 7.4.4. update fatal error’ is closed to new replies.