How To: display current HTML site while building WP in the root?

Install WP in a sub-folder, then when you ready to launch the new site on root, see Giving WordPress Its Own Directory.

Right. What about the files left on my computer? All the permalinks within my files will be wrong.

Let me correct the above post. I have read the post at the link you reference above. I see how moving the .htaccess and index.php files will allow the core pages to be accessed.

My question is, after updating the URL and the permalinks, will people still see the sub-directory name in the displayed url ex: domain.com/Wordpress/about_us or will it be domain.com/about_us? Are the pathways updated and hidden with the .htaccess changes?
Thanks you for the instructions.

J

It will be domain.com/about_us

Are the pathways updated and hidden with the .htaccess changes?

What do you mean by “pathways”?

You answered my question. I mean the file structure url domain.com/fhslfhadkf/khfdfh/jdfkjda.

Specifically, after initiating the update to the root directory as specified above, in my browser will I have problems trying to load cached pages of the site that I developed? Before “Going Live” I would have /Wordpress/about_us to view changes to the page or the site after altering the code and uploading pages via FTP. Will that still work? I’ve had problems before even after clearing browser history and cookies. Or will the .htacess override that request and return a 404 response?

You will be able to review the site in the sub-folder prior to making the change to allow it to take over the root domain, yes?

Yes. One of our developers is convinced that there will be an issue with his browser, trying to live edit the WP files after resetting the URL and moving the index.php and .htaccess pages.. He claims that that all the cached pages will no longer work. That he will have to retype the the the full url each time minus the /Wordpress. True? Or will /Wordpress/about_us still pull up the page, given that the core WP files still live in the sub-folder?

I know it is minor, but we started to look for a way to install in the root first so the cached pages would remain the same after going live. That is why we were looking for a way to display the existing HTML site. I have to manage these petty complaints to get everyone happy.

Thank you for your repsonses.

He claims that that all the cached pages will no longer work.

Is he referring to hos browser’s local cache? Or is the site using a caching plugin. If it’s the former, he can clear his cache (although many developers turn browser caching off when working). If it’s the latter, you should be able to flush the plugin’s cache – although I’d recommend checking the plugin’s documentation about this.

That he will have to retype the the the full url each time minus the /Wordpress.

Sorry but that’s simply not true. Your About Us page will run from /about-us once the move has been completed.

Put it this way – I’ve developed completely new sites in a sub-folder whilst an older WP site was running in root. When we were ready, the old site was pulled down and the sub-folder site re-configured to take over root – using exactly the same method I mentioned above. The new site ran all of the old page urls without the slightest problem.

well i too would like to move my files as a friend uploaded his old drive into my computer or rather replaced it and all my documents are gone.
and my old name was barbaragreenemann, does that make a difference? and i was resetting my PW as Eq5d)JE&etNT you sent this one to make the change.hope this will help mt blog place
barb mann

@barbara greene mann: It is impolite to interrupt another poster’s ongoing thread with an unrelated question of your own. It causes significant problems for the forum’s volunteers and prevents us from being able to track issues by topic. Please post your own topic.