[KCooper]

Hi guys,


I'm just about finalising an ecommerce site for a customer.

The domain name that they want the ecommerce site positioned at currently has a wordpress site in its place.

My question is, how would I go about moving the current wordpress based site across to another domain, so that I can place the ecommerce site in its place?

Is it just a case of backing up then reinstating the database information (via MySQL PHP myadmin) into the database on the new server, and FTP-copying all the files/folders from the old domain onto the new domain? Would it just work straight off the bat or is there anything else I need to be aware of? Never had to do this before, so a bit apprehensive...

Just to make clear, I'm not after advice on getting the ecommerce site working on the domain name, just how to move the old Wordpress site onto a new domain/database.


Thanks in advance,

Kyle

[bocaj]

It'd probably be easier to put the commerce site on a server, and then just point the domain to the new server.

Just my $0.02

[KCooper]

Well the ecommerce site is currently on the same domain as the Wordpress site, just under a /shop extension, and utilizing a different database.

Once the Wordpress site has been moved, the root domain will be replaced by an entrance page I have coded up.



Kyle

[iksol]

KCooper, on 28 August 2010 - 12:02 AM, said:

Is it just a case of backing up then reinstating the database information (via MySQL PHP myadmin) into the database on the new server, and FTP-copying all the files/folders from the old domain onto the new domain? Would it just work straight off the bat or is there anything else I need to be aware of? Never had to do this before, so a bit apprehensive...

that's what I normally do.

Backup DB.

Create new hosted site, create new DB, restore DB

Copy WP files. Update wp-config.php with new credentials.

That should do it.

[iksol]

Also, should've mentioned...

If you're unsure of this, try it out on a temporary site so you're confident it'll work.

I usually create a temp site on ######s.com, which is free. Then delete it.

[iksol]

iksol, on 28 August 2010 - 08:13 AM, said:

Also, should've mentioned...

If you're unsure of this, try it out on a temporary site so you're confident it'll work.

I usually create a temp site on ######s.com, which is free. Then delete it.

OK, I guess I'm new here so can't be posting URLs, tut tut. PM me if you want to know a free web host for testing a Wordpress restore.

[bocaj]

iksol, on 28 August 2010 - 08:16 AM, said:

OK, I guess I'm new here so can't be posting URLs, tut tut. PM me if you want to know a free web host for testing a Wordpress restore.

Odd. I swear it's never hashed out urls before, maybe it's a new feature

[pat24]

bocaj, on 28 August 2010 - 01:12 PM, said:

Odd. I swear it's never hashed out urls before, maybe it's a new feature

I think it only hashes out if there is a rude word in the url like s****horpe.com

EDIT: apparently not hashes then

[iksol]

I think it's just because I'm a newbie on here that URL got hashed out. I'm sure the rules don't forbid *all* URLs.

The website is ######, followed by a dot com. And it is free to use, although not the most reliable, but what do you expect for free :-)

[KCooper]

Hmm, thanks guys.

Well I'm going to be moving it on monday, so hopefully all goes well!


Kyle

[KCooper]

I've just copied ALL the files and folders via FTP onto the new domain name/server, copied the database over and sorted out the .htc access file so it is correctly connecting to the database.

The index page is displaying correctly, but every link I click on takes me back to the original site, so...

newdomain.com is set up correctly, a direct copy of olddomain.com. But when I click on newdomain.com/page1, newdomain.com/page2 etc, it takes me back to the old site. As I said, the database has been copied over correctly and connected, and I would have thought the site links would have been relative, not absolute... Also, if I manually type in newdomain.com/page1, I get a "not found on this server" error message.

Any ideas how to rectify this? I'm not too hot with WordPress...

Thanks in advance guys,

Kyle

[pat24]

KCooper, on 30 August 2010 - 10:54 PM, said:

I've just copied ALL the files and folders via FTP onto the new domain name/server, copied the database over and sorted out the .htc access file so it is correctly connecting to the database.

The index page is displaying correctly, but every link I click on takes me back to the original site, so...

newdomain.com is set up correctly, a direct copy of olddomain.com. But when I click on newdomain.com/page1, newdomain.com/page2 etc, it takes me back to the old site. As I said, the database has been copied over correctly and connected, and I would have thought the site links would have been relative, not absolute... Also, if I manually type in newdomain.com/page1, I get a "not found on this server" error message.

Any ideas how to rectify this? I'm not too hot with WordPress...

Thanks in advance guys,

Kyle

Have you changed these lines in wp_config.php to the new domain

define('WP_SITEURL', 'http://www.example.com');
define('WP_HOME', 'http://www.example.com');

[KCooper]

pat24, on 30 August 2010 - 11:05 PM, said:

Have you changed these lines in wp_config.php to the new domain

define('WP_SITEURL', 'http://www.example.com');
define('WP_HOME', 'http://www.example.com');

Those lines weren't already present in the wp_config.php file.

I added them in, and now the links all appear correct (ie, newdomain.com/page1) and no longer point to the old domain, but now they all provide the message "the requested url was not found on this server".


Thanks for the help so far though, mate.

Kyle

[pat24]

KCooper, on 30 August 2010 - 11:17 PM, said:

Those lines weren't already present in the wp_config.php file.

I added them in, and now the links all appear correct (ie, newdomain.com/page1) and no longer point to the old domain, but now they all provide the message "the requested url was not found on this server".


Thanks for the help so far though, mate.

Kyle

you might also have to edit the database

the table wp_options or wp1_options their will be a site url field that will have to be changed also check the home field

if that fails try this plug in

http://www.velvetblu...in-update-urls/

[KCooper]

pat24, on 30 August 2010 - 11:30 PM, said:

you might also have to edit the database

the table wp_options or wp1_options their will be a site url field that will have to be changed also check the home field

if that fails try this plug in

http://www.velvetblu...in-update-urls/

This appears to be more or less working now.

Thanks so much, mate.

For clarity:

I installed and utilized the above plugin, then I also had to change the "perma links" setting via the admin backend to thier defaults.


Kyle

[pat24]

KCooper, on 31 August 2010 - 07:11 PM, said:

This appears to be more or less working now.

Thanks so much, mate.

For clarity:

I installed and utilized the above plugin, then I also had to change the "perma links" setting via the admin backend to thier defaults.


Kyle

Glad you are sorted. where about in S.Wales, I am in Chepstow

[KCooper]

pat24, on 31 August 2010 - 07:21 PM, said:

Glad you are sorted. where about in S.Wales, I am in Chepstow

I lived in Cardiff for a while while at uni mate, I'm back in Bridgend now though - looking to branch out again when I get a job sorted though :-)

[JohnJo]

The most descriptive solution to this problem that I have found is here.

The problem is that within the wordpress database there's a collection of URLs pointing to the site that the content was developed on. All these URLs need changing to the new domain url. A particular problem is the length encoding that occurs on a few of the urls. The article will explain this.

I am currently developing wp content on localhost.com for my company and I've tested moving the wordpress database onto a live internet hosted site by editing URLs within the db and it worked.

FYI, the text editor I used to edit the sql db export before importing it again with the desired domain name was emacs.

Hope this helps.