By splashworx on

In a perfect world I would like to migrate my test site to the production host/server. It looks like a nightmare so I've decided to rebuild the site from scratch (not too much of a drama, time-wise).

After months of trying to get Clean URLs working on the new production location, I discovered that the URL of the production site is not liked by Apache's mod_rewrite module because a domain is not delegated yet. The URL I have is http://romana.webcity.com.au/~gre49867/d613 instead of the friendlier http://www.example.com/drupal.

I'm unable to re-delegate the client's domain name to the new production host/server because I have their domain currently pointing to the test site (yes, I am a twit, I originally built the site on my personal host account/server in the belief that I could simply move the site across to the new server with minimal fuss. I know it can be done but the first few attempts were a nightmare so I decided to build the site again from scratch. It's a good excuse to upgrade from D5 to D6).

So before I begin to build the new site on the client's host account/server, I need to know if after I delegate their domain name to the new site, will this screw up the node URLs in any way? This especially counts if I'm able to switch on Clean URLs after the domain is delegated.

I've played around with the .htaccess file for the server/sub-domain to 'adhere to' (per my example above) but Clean URLs still won't come to life. The host account tech-support guys confirm that the mod_rewrite module isn't liking the URL I'm stuck with (until domain delegation, that is).

Any .htaccess / Clean URLs experts out there?

Going grey...

⋅ Categories: Drupal 6.x

Comments

vm’s picture

vm commented

you have to point the domain name servers(DNS) to the new host. This can usually be done at the registar where the domain name was purchased.

splashworx’s picture

splashworx commented

Thanks for the reply. I understand that I need to point the DNS to the new host but when I do so, will that affect the production site's ability to access nodes correctly? That is, the production site will be built using the horrible URL and once the new site is finished, THEN I point the DNS to the new host - changing the URL and paths (I assume).