Regarding the functions.php file section, couldn't that be achieved by adding a few lines of code to the wp-config.php file? ChrisThomson 20:17, 6 October 2008 (UTC)

(in my opinion) a more reliable way to adjust the database

I've had most success with this method: 1. Export the DB in something like phpmyadmin or mysqldump 2. With a text editor do a search and replace of old domain and new one (making sure you search for the right domain inc. subdomain). 3. Move your wordpress install and use this new database. This is more effective because it also changes plugin data. Netweblogic 18:53, 11 August 2010 (UTC)

totally confusing

Allright, i tried to figure out what i need to do to solve my problem but i couldnt find the right answer on this page because its not written for idiots. And most people are, including me :-)

What i need is a title like:

1. Move your blog (the files) from one server to another, keeping the url
2. move your blog (the files) from one server to another and change the url
3. move your blog (the files) on your server into a subfolder/subdomain, keeping the url
4. change the domain of your blog without moving it (files remain where they are)

The last point is my actual problem i want to solve and i canot figure out what i have to do because i canot handle that it goes right into changing the wp-config.php. But how do i know it solves my actual problem?

(New user--previous guy didn't sign his post, and unlike Wikipedia this forum doesn't do it automatically if you fail to do it manually.)

Okay, there's this text at the start of the article:

• The "Home" setting is the address you want people to type in their browser to reach your WordPress blog.
• The "Site URL" setting is the address where your WordPress core files reside.

So it sounds like "Home" is the more benign of the two settings (just "the address you want people to type"), and "Site URL" is the dangerous one (where "core files reside"), whereas the much better-written Giving WordPress Its Own Directory, which I more recently have found, seems to indicate the opposite. After reading the present article's introduction (just got confused by the body of the article), I changed "Home" only and my site crashed. Thanks.

Then I read:

You should not attempt to use this additional information if you're only attempting to correct a "broken" site.

It almost sounds like it's saying the article is of no use for fixing a broken site. Here the article should say more about how this "additional information" is marked off in the text of the article.

I've attempted to correct some of these shortcomings in the article--rather unskillfully. My hope is that someone more knowledgeable will come along soon to remedy them.

Yes, after all my stupidity, I'm fool enough to sign this testimony against myself. Jwk 10:08, 1 November 2012 (UTC)

Indeed

The whole page needs redrafting I think, it's on my to-do list but haven't got around to it yet. mrmist

Editing the SQL file?

I've had trouble with the "edit the .sql file" method of changing the URL that's embedded in post content and other areas. It seemed to have a problem when the address was embedded in serialized data, and back in the day when there was some character set switching (Latin1 to UTF8) I don't think my editor handled all those codes correctly. Converting2wp 21:58, 7 April 2012 (UTC)

Never, ever change GUID?

Hmmm...

If changing the web address of a live site because of a rebranding, I can see the point.

But if moving from testing-server-during-initial-install.mysite.org to mysite.org? Where's the harm of cleaning the cruft out of the GUID entry. Presumably no one had subscribed to the testing server's RSS feed. Converting2wp 22:03, 7 April 2012 (UTC)

Home or Site

OK I'm a first time user setting up a site on a hosted domain for the first time.

I appear to have conflicting advice from Codex and from the Wordpress Dashboard Panel...

http://codex.wordpress.org/Changing_The_Site_URL says:

The "Home" setting is the address you want people to type in their browser to reach your WordPress blog.

The "Site URL" setting is the address where your WordPress core files reside.

Wordpress Dashboard Settings General says:

Site URL Enter the address here if you want your site homepage to be different from the directory you installed WordPress.

So are the core files or the content to be viewed stored a Site?

I want the public to see the site at www.retrailsforwestberks.net not ....net/wordpress and I have already locked myself out of the dashboard by changing the URLs without knowing what I did.

Provide advice for Jetpack 2016

This page is the top Google hit for "wordpress change domain".

It needs some information about what to do if you are running Jetpack, and what to do if you are running Photon.

We just tried to migrate our site from a development server to the official domain, using the instructions given on the page. But we suffered the following problems:

1. Jetpack disconnected. This "well known" problem might not be well known to people reading this page! (In fact, the last time we made a duplicate of a live site, Jetpack disconnected on the original domain, so we lost all its stats!)
2. Our images became broken. Apparently Photon had been storing our images at `i2.wp.com/our_old_domain/...`. When we changed our `siteurl`, WordPress started pointing to non-existent paths on `i2.wp.com/our_new_domain/...`.
3. To fix that, we were advised in IRC to disable Photon. When we tried that, we discovered that not all our images were actually in `/uploads`.

It would be great if this page could warn about potential problems that can arise for people running Jetpack, and if possible how to work around them.

-- Cheers, Joeytwiddle (talk) 14:53, 11 April 2016 (UTC)