Hi,
I've just successfully migrated a site from Mambo to Drupal (actually it's CivicSpace 0.8.0.3) and firstly I'd like to say thank you to everyone who has worked so hard on both the Drupal project and latterly CivicSpace. I've done a couple of Drupal installs in the past just to see what it was like and have a play but this was the first time I used it in anger and it rocks!
So anyway I just put the site I have been working on live and the shared host that it is on started producing a high load in Apache. The hosting company contacted me to tell me this and mentioned that they had traced it down to the mod_rewrite rules being used by Drupal so they commented them out. The host is Webfusion (aka Host Europe, aka Pipex). I was wondering if anyone had come across this before or had any ideas about this. Not having any more details from the hosting company and hot having very much access to the machine makes it hard to do much else. I'd like to re-enable clean urls at some point in the future and was hoping someone would have some advice or tips. I've searched the site and can't find anything of use.
Thanks in advance, looking forward to the replies (if any!)
Cheers
George
Comments
I've had a similar problem
I've had a similar problem once and it turned out that I had the RewriteBase set to a wrong value.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
Oooo thanks...
Thanks for the tip. I think the RewriteBase was just set to "/". Maybe I should set it to the full path and see if that works.
Cheers
George
interesting problem, let us
interesting problem, let us know how that works out...
Try putting rewrite rules in httpd.conf
Ask your host if they can put the rewrite rules in the apache config rather than in .htaccess. This should make it a bit faster.
You will need to modify the rules. I have to go now, but I'll post the rules I use later.
I had similar hosting issues
I had similar hosting issues when I was playing with the rewrite rules to redirect some old pages to the new site. Fortunately I had a local test server where I could check the logs and see that Apache was segfaulting over some sort of redirect loop. So I tweaked it until it stopped crashing and haven't gotten any complaints from the host since.