-
☆ A M B ☆
- 24,524 Posts
I find developing on the remote site advantageous also.
What I do is create a nice "site unavailable" document and put it up. If the client already has a live site at the domain, I simply make my "site unavailable" page a redirect to their existing home page.
This way, to see the new site under development, just log in to the manager, and then enter the new home page in the browser address bar manually.
Of course, if their existing site works off of an index.php file, that’s another story, but so far very few have. I don’t turn on friendly URLs until the new site has gone live.
One disadvantage to this that I’ve discovered is that it is necessary to have a robots.txt file denying your index.php file to Google and friends, since they’ll spider your development site and have all the wrong URLs by the time you get the new site live.
-
☆ A M B ☆
- 24,524 Posts
Well, I can’t really take the credit for that one, I was doing freelance work for a local developer, EGStudio, and their client was a big-time SEO consulting company, so they got all hot and bothered when they saw Google pages for the dev site pages.
I do have one recurring problem, when I change my resource path and file manager paths from C:/wamp/www/mysite/ to the live site url, I lose the File manager tab in Configuration and have no files under Resources/File Manager.
Well bugger me (as we say in Oz) I left it alone for a few days and it fixed itself.
"Is it magic, master?"
"No my young apprentice, it was most likely some sort of caching issue."
Still, I could have done without the hours of reinstalling to try and sort it out.
And before somebody says it, I was hitting the purge button continually.
Content Creator and Copywriter
I also like to develop on the remote server as much as possible.
