WordPress.org

Ready to get started?Download WordPress

Forums

WordPress Admin Directory Error (14 posts)

  1. nfischer83
    Member
    Posted 8 months ago #

    So I built a new website for a client inside of a sub-domain in order to preserve their current website while the new one was built. Once I was ready to launch the website, I went into my WP Admin panel and changed the primary links in the setting to be the primary domain instead of the sub-domain. It kicked my out as expected because the folders haven't been moved yet. So I log-in to the hosting and file manager. I move the old website into a backup folder and then I move the new website into the root directory. The website it now live and seems to be working okay. But when I try to log into my WP Admin panel, it seem to be looking into the old /test directory and I can't figure out why it's doing that. This is the error that I receive:

    Warning: require_once(/home/content/85/8452185/html/test/wp-includes/load.php) [function.require-once]: failed to open stream: No such file or directory in /home/content/85/8452185/html/test/wp-load.php on line 42

    Fatal error: require_once() [function.require]: Failed opening required '/home/content/85/8452185/html/test/wp-includes/load.php' (include_path='.:/usr/local/php5/lib/php') in /home/content/85/8452185/html/test/wp-load.php on line 42

    It's strange because it should not be looking inside the /test folder anymore. I moved all the files out of there and into the main directory. I even tried deleting that folder completely to see if it would fix it. It didn't.

    I've tried called my hosting providers support but they have no idea what happened and believe that it's a coding problem within WordPress. I disagree.

    Any ideas or advice?

    Thanks!

  2. esmi
    Forum Moderator
    Posted 8 months ago #

    I moved all the files out of there

    When you did that, did you follow the relevant instructions in Moving_WordPress?

  3. nfischer83
    Member
    Posted 8 months ago #

    Yes. I'm pretty sure. I selected every singe file and did a move into the root directory. Unless there is something that I'm not understanding about this process?

  4. esmi
    Forum Moderator
    Posted 8 months ago #

    So you followed all 14+ steps in Moving_WordPress? Only just moving files & folders is nowhere near enough.

  5. nfischer83
    Member
    Posted 8 months ago #

    Yes. I followed all of those steps. I've done this multiple times on many different sites and have never had this problem. This is the first time I have ever seen this.

  6. nfischer83
    Member
    Posted 8 months ago #

    Besides "restarting your server". I have no idea how to do that. It's not my server. It's on GoDaddy.

  7. esmi
    Forum Moderator
    Posted 8 months ago #

    Where on Moving_WordPress does it mention "restarting your server"?

  8. nfischer83
    Member
    Posted 8 months ago #

    Step 14. Sometimes you would need to restart your server, otherwise your server may give out an error. (happens in MAMP software (Mac)).

  9. esmi
    Forum Moderator
    Posted 8 months ago #

    That's only if you are hosting locally - which you are not. So you carried out all of the other 13 steps?

  10. nfischer83
    Member
    Posted 8 months ago #

    yes.

  11. esmi
    Forum Moderator
    Posted 8 months ago #

    To be honest, I'm not sure which step(s) you have missed or perhaps misunderstood but it does seem that at least 1 step wasn't carried out correctly.

  12. nfischer83
    Member
    Posted 8 months ago #

    Okay. So after I just confirmed to you like 4 times that I have followed each step, you telling me that I missed a step? lol

    I have done this before. It's not like I'm brand new to doing this.

  13. Nikole Gipps
    Member
    Posted 3 weeks ago #

    Did you ever find the answer to this? I think the key to this is GoDaddy because I have done this 100s of time as well and never hit this issue until this GoDaddy server.

  14. Nikole Gipps
    Member
    Posted 3 weeks ago #

    So I found out it was somehow the public wifi I was on causing the issue ... I didn't know it was possible to cache things in that way? But using another computer/network worked fine. I can't explain it. And yes I'd never seen that before.

Reply

You must log in to post.

About this Topic