Facebook
Twitter
Chris1
Regular Pleskian
A client of ours installed Wordpress via the "Applications" section in Plesk 10 at "example.com/wordpress".
When the customer had finished creating the site, we ran a script to change all instances of "example.com/wordpress" to "example.com" in the database and also moved the website files to the root directory in "httpdocs".
This worked well until we had to migrate their site to one of our new Plesk 12 servers. It seems that during the migration process it has put back in all of the instances of "example.com/wordpress" in the database therefore causing the website not to load correctly.
Why is the migration tool doing this?
When the customer had finished creating the site, we ran a script to change all instances of "example.com/wordpress" to "example.com" in the database and also moved the website files to the root directory in "httpdocs".
This worked well until we had to migrate their site to one of our new Plesk 12 servers. It seems that during the migration process it has put back in all of the instances of "example.com/wordpress" in the database therefore causing the website not to load correctly.
Why is the migration tool doing this?
