• Resolved Jim McLaughlin

    (@jimmcl61)


    I receive this error after attempting to move my WP site from subdirectory (wp) to the root.

    Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0

    Fatal error: Unknown: Failed opening required ‘/home/corps/public_html/wp/wordfence-waf.php’ (include_path=’.:/opt/cpanel/ea-php74/root/usr/share/pear’) in?Unknown?on line?0

    I had deactivated and uninstalled WF before the move.

    What else am I not doing right?

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Jim McLaughlin

    (@jimmcl61)

    This is definitely a Wordfence migration issue. This error shows up often. Sorry for the bother.

    For folks who got this far, when you deactivate WF, you will be walked through a series of steps that will remove WF properly, allowing for the director migration to happen. If I get other errors, I’ll update this, but assume that a proper deactivation of WF before migrating the directory works as WP says it does (which is quite easy, otherwise).

    [Update: no errors now, though I can’t access site-editor.php for some reason.]

    Plugin Support wfpeter

    (@wfpeter)

    Hi @jimmcl61, thanks for your messages.

    The most common issue seen when migrating from a development environment to a live site (or from one host to another) is when Wordfence is optimized, as the path to your wordfence-waf.php file is not likely to ever be the same.

    The default state on installation is that the firewall is in “basic protection” mode, so keeping it this way until the site is live should ensure the migration doesn’t break anything on your site. It’s highly recommended to optimize once the site is live! You can also remove an existing optimization from a live site before moving it to a new host.

    You can also check our migration documentation for further detailed information: https://www.wordfence.com/help/advanced/remove-or-reset/#migrate-with-wordfence

    Thanks,
    Peter.

    Thread Starter Jim McLaughlin

    (@jimmcl61)

    Very helpful, and I wish I’d done that. I still haven’t figured out how to fix my browser, which is somehow blocking access to the site editor when not in debug mode. (Removing cookies doesn’t help. A never-ending saga.)

    But many thanks, @wfpeter!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error after moving directory’ is closed to new replies.