This thread on the support forum looks like it could be useful for people having trouble with installation. Do we need to update the instructions? - Jalenack 10:15, 14 Jul 2005 (UTC)

Ouch! It's my bad, my mistake, I shouldn't have to do this, but ouch! I want clarity here, not ambiguity. You tell me where to go in Admin, I'm there. You tell me to change the two URIs, I'm with you. But when what I find is two URLs, I'm wondering what's going on. And I don't want to wonder. I want clarity. And yes, there's a good chance that because you're expert and could do this in your sleep you see me as showing how stupid and inept I am. But I'm not expert. If I could do this in my sleep I wouldn't be sitting here keyboarding in Codex after coming to Codex for detailed instructions. see http://bentrem.sycks.net/images/wp-move.jpg ... I see two URLs. Is that what you mean? You went to the trouble of being precise: URI is what you wrote. Please correct / clarify / update, whatever. In the meantime, I'm screwed and I stay screwed. *OUCH!* --bentrem 19:30, 20 July 2010 (UTC)

I had someone on Twitter question my contra-distinction, someone who knows his craft. Off the cuff I would have said "If you want URL then you'll get something like http://bla-yada or ftp://yada-blah; if it looks like a directory then it's URI, not URL. But heh URL is a URI too! But not all URIs are URLs. Not all dogs are fine handsome English Springer Spaniels." Instead I looked, found, and quoted TimBL.

So: if WP3 just wants the URL, then happy happy happy I don't have to change a thing all I need do is re-direct that domain, move the files, and I'm off to the races. And if it requires the URI then fine I will scrupulously enter the correct URI, pointing to the new directory in the new directory (which is being mapped to that URL) and then move the files.

Either way. But don't please don't state the requirement ambiguously. If it's URL you want, please say so. If any old (correct) URI will do then fine, I'll leave it as http://my.domain.com ... right now I'm not sure that's ok.

And yes, from my reading, if I move the files and make a mistake that will corrupt the database.

So it matters to me. (It's already a dog's breakfast because import from Livejournal failed in mode X and import from Blogger.com failed in mode Y, the consequences of which I gave up trying to correct.) --bentrem 23:10, 20 July 2010 (UTC)

Moving within your own site: an alternative

Here is an alternative method for section 1 (moving within your own site). I'm not sure if somebody wants to add it to the actual article, but feel free to do so.

1. Through your website's control panel, go to the MySQL section and open phpMyAdmin.
2. In the left-hand sidebar, choose the appropriate database from the dropdown menu.
3. When the list of tables loads in the left-hand sidebar, click "wp_options" (the word itself).
4. In the tabs along the top of the right-hand frame, click Browse.
5. Find the row with the option_name "siteurl" and click the blue pencil in the far left of that row.
6. Change the option_value to the new location and click "Go" at the bottom of the page.
7. Find the row with the option_name "home" (it may be on a subsequent page) and click its blue pencil; again, change the option_value and click Go.
8. Move the entire old directory to its new location, either by renaming the directory itself or moving the contents to a different folder.

Note that any direct links, such as to images you have uploaded, will be broken during this process. You should change direct links to point to the new location.

-Etoile 03:39, 2 Jun 2006 (GMT)

Please clarify latest revision

Please explain what this means.

<< not WP3 compatible

What is not compatible?

Changed it

I've removed those notes from the page. Reading on this page it seems to relate to some symantic debate around URL and URI. Since many folk reading this don't care either way, I think it's best to avoid further confusion by suggesting that bits are "not wp3 compatible", at least until there's further explaination.

mrmist

Wondering if we can remove "Step 8: WordPress 2.0 only: Delete the folder wp-content/cache." from the list of items for Moving Within Your Site. Are there a lot of people still on 2.0? Tw2113 22:20, 9 November 2011 (UTC)

Different method?

I've had to do this recently, and after googling, found a different method. It seems to me that the process listed on askwpgirl.com is a lot simpler and doesn't require messing about with the database directly. Possibly this page should be updated to include this way? --softlord 15:04, 14 January 2013 (UTC)

Installing a downloaded version of a WP site to a local host

I'm attempting to install a WP site to a local host that I had backed up from an automated backup plugin. I've had this site backed up on a hard drive for sometime and would like to install it to a subdomain as an example of work. Unfortunately, I backed this site up before I knew anything about databases and how to migrate WP from one server (or a local host) to another server. I am now comfortable with that process. However, I seem to be having some difficulty establishing a database that is recognized by MAMP.

Background story (Or: Why so complicated?)

Hi,

I am just about to take over a couple of wordpress customers and was wondering why they have installed their WP in the docroot-folder. Now I know, and with help of the codex now I have an idea how to change it (put installation to subdirs and change the docroot). What I am wondering about: Here are a lots of situation how to handle what case, but I am missing some background, what each of the both database-entries are for, what the problem with permalinks is about and so on. I think that might help in resolving special situations. So if anybody is deep enough into WP, it would be very appreciated adding this knowledge !! Dominic.Kuechler (talk) 12:05, 9 May 2015 (UTC)

Changing Your Domain Name and URLs

I'm removing the note to only search and replace in wp_posts table. I've seen URL references in several other tables. They could easily occur in other options or any of the meta tables. Strictly adhering to this note could break a site. It needs to go.