Wordpress Migration

zequestioner
zequestioner used Ask the Experts™
on
Hello Experts,

I am migrating a wordpress website from one hosting company (Host1) to another (Host2). From Host1, I made a copy of the root directory and dumped the db in a .sql.

I then installed a fresh copy of wordpress on Host2, then used FTP to 'overwrite' the root directory of the clean install with the root directory from Host1. I then imported the database on host2 and edited the wp-config with the new db info. (dbname/user/pass/dbhost)

The hosting company said this should have worked, but I'm getting an error on the webpage that says:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Did I miss a step?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Jason C. LevineDon't talk to me.

Commented:
Three things that may have gone wrong.

1) you don't need to FTP all of WordPress, just the wp-content folder. You may have brought over something else you didn't need to and that could cause a 500

2) You need to edit the .sql file and make sure the file paths are changed from host 1 to host 2.  Those paths are used by plugins and can cause problems if not changed.

3) Did the FTP copy PHP as ASCII and other stuff as binary?

Author

Commented:
Wow, sounds like a lot of work... do you know how many places I would need to change the file paths in the DB? Is there a list of this somewhere?

Author

Commented:
I did edit the index.php:

/** require('./wp-blog-header.php');  */

require('./newSite.com/wp-blog-header.php');

Since on my new host, I'm setting up individual folders for each website on the new domain. This is the first site..

What's weird is if I leave it as default (currently commented out) that gives the error.. but if I change it to the latter, the site comes up with a blank page. When I view source there's a blank line 1 and nothing else...

Thoughts?
Angular Fundamentals

Learn the fundamentals of Angular 2, a JavaScript framework for developing dynamic single page applications.

Author

Commented:
Note, when installing wordpress, I did set it to point to the correct folder as the default root directory for wp.
Jason C. LevineDon't talk to me.

Commented:
It's not as much work as you think.  I wrote an article a while back that deals with exactly how to do this:

http://www.experts-exchange.com/Web_Development/Blogs/WordPress/A_10258-How-To-Move-A-WordPress-Site.html

Since you are not changing domains, just skip those steps.  But all the others apply.

Author

Commented:
Thanks for the info.. for some reason I'm still having problems. The site comes up (with the default wp theme) and the /wp-admin throws the same error. Any thoughts?
Jason C. LevineDon't talk to me.

Commented:
Because something is still not changed over to use the server 2 environment.

Author

Commented:
Bwp debug says there is no lib folder on the theme.. but there isn't. Can I remove the runonce function?
Jason C. LevineDon't talk to me.

Commented:
No idea.  Don't know what theme you are using , have no way to test your exact setup...

Author

Commented:
My apologies... here is the exact error from the wp debug. My question is this... what is the file I should look at, which references 'line 3'.... and is there a way to bypass the Warning: require_once since setup has already been run...

Here is the rest of the error:

Warning: require_once (some/path/wp-content/themes/crystal/lib/init.php): failed to open stream: No such file or directory in /some/path/wp-content/themes/crystal/functions.php on line 3 Fatal error: require_once(): Failed opening required

The weird the is that I've looked through the db file and cannot find references to /some/path since I've changed everything to the root path. /wp-everything....

Hope this helps.
Don't talk to me.
Commented:
Server paths don't work the same way as URLs.  Changing everything to /wp-everything will break include and require statements.

/some/path/to/wordpress from server 1 needs to become /some/other/path/to/wordpress in order for things to work. This means you have to know what the new path is (use the pwd command on server 2)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start Today