Question about redirects
I would like to replace a website with a Wordpress installation, but still keep the original site available during the Wordpress build.
I did a 302 wildcard redirect of the site to a duplicate of the website. I deleted the files in the main site and I'm ready to install Wordpress.
The redirect works well - in fact, too well for my purpose. I can't access cpanel for the website, no doubt because of the redirect. So I can't install Wordpress with this approach.
But even if I could, I wouldn't be able to access the wordpress pages because I am redirected on every attempt. Even trying to access the account name redirects me.
Is it possible to do this at all? Basically, I want to keep the current site available while the revised site is built on the domain.
Hello! There is a very easy way of doing this. Simply install wordpress on www.yoursite.com/wordpress just make a folder called wordpress install it there. When you are ready to move it just go into the admin panel and click change web address Hope that helps. Then with the redirects it won't matter.
Originally Posted by DrayScherm
1 - Yes you can still access your cpanel and bypass your domain redirect:
Originally Posted by DrayScherm
Use the IP or server name (ask your host for this if it was not included in your welcome email).
The url will look like 000.000.000.000:2082 or 000.000.000.000/cpanel or servername.com:2082 or servername.com/cpanel
2 - You can install wordpress from fantastico within your cpanel into any directory of your choosing, and that means the web root directory if you want it there.
(If you install in web root, you may need to rename your landing page and set up .htaccess with the directory index to the new name so you can work around the default index.php/index.html protocol, as well as any links directing to it.)
3 - Moving wordpress is not quite as simple as Palmer mentioned, but doable:
You will need to go into your MySQL database through phpMyAdmin and modify two fields in the wp-settings table for your wordpress - URL and Home.
Be prepared for wordpress to break if you do plan to move it. It can happen and if is fixable so don't panic. I've moved many wordpress sites for others, and my own has moved a couple times. I even had a trainer purposely break it, then I restored it (perhaps a little different than the trainer expected, but it was successful).
4 - Accessing wordpress around redirect:
You can use the same temporary URL as mentioned for cpanel access, you will need to change the Home and URL fields in the phpMyAdmin temporarily for wordpress login purposes, then change back once you have removed the redirect.
Last edited by Refiner; 11-21-2011 at 05:21 PM.
Reason: added #4
When you say, replace a website, do you mean replace the content? Scrap it and start over? If not, I'd get everything restored and put wordpress in a folder thesite/wp/.
If you're planning on moving all the content (text.html) onto wp posts and pages you've got your work cut out for you. The real redirect fun will start then. Can't think of why anyone would want to do this.
WordPress Sub-directory Move
I would agree with palmer, wordpress allows you to easily install its files in an outside directory and display the actual blog elsewhere whenever you choose. The best thing about this approach is that you avoid having to make any DNS changes which can cause propagation time for 24 - 48 hours and that can mess you up a lot while working on setting up your new website. I would do the following:
1) Place your old site back to root and remove the 302 redirect as if you were putting the website back for good
2) Upload a fresh batch of wordpress files to a sub-directory such as the above mentioned /wordpress/ or /wp/ examples (you can also use your own custom name to make your WP install more secure from hackers or competitors)
3) Create a fresh database for wordpress and setup the WP config file (do not use quick install apps in cpanel for the WP install, upload fresh files as this is safer and more secure)
4) View and work on your website in development via your regular web URL after adding the sub-directory name to the end of the URL (so yourdomain.com/wp/ would be where you view your new website until complete)
5) Leave your files in the same outside directory, then change the wordpress blog URL to your root and set the .htaccess redirect that is described on this codex.wordpress.org/Giving_wordpress_Its_Own_Directory
6) Make sure everything works and then delete the old site to clean up your root, wala! You have wordpress running the show now!
Note: I would setup a redirect for your most important links and pages and then I would set a catch all redirect as well as an optimized 404 page [mod removed unauthorized URL] built right in wordpress in which I chose to use Contact Form 7 and place the following codes in the message body of the email lead:
Form Submitted From: [_url]
User Remote Ip: [_remote_ip]
This will tell you exactly the full URL of any page that somebody hits a 404 page and all they have to do is click the send button, no other information is needed. I use the ip to have the ability to block certain ip's if needed. Over time this will help you make the complete move to using wordpress for your site well worth the effort. Hope this helps.
Last edited by weegillis; 11-25-2011 at 05:20 PM.
Reason: Missed a couple words.; [URL removed by mod]
Wow, this has been a great help! Many thanks to all. Very much appreciated.
Tags for this Thread