Posted by Transmitter on October 5, 2010 at 2:05am
Hi everyone,
my status page tells me, my .htaccess file is wrong for boost.
### BOOST START ###
### BOOST END ###
Copy this into your .htaccess file below
# RewriteBase /
and above
# Rewrite URLs of the form 'x' to the form 'index.php?q=x'
But this is exactly what I've done and what I can see within the file.
What am I doing wrong?
Thank you in advance
Bye, Transmitter
Comments
I've had this before. I am
I've had this before. I am not sure why but I found verifying the platform and then the sites affected once I had edited .htaccess to make sure it matched the boost .htaccess rules page seemed to resolve that error and I started caching again. I only had to do this once when importing the platform and site.
HTH,
JamieT
Dev Boost
Current dev version of boost has some big changes to the htaccess file. It's backwards compatible so if you don't change it nothing bad will happen.
http://drupal.org/node/856880
http://drupal.org/node/764494
Hmm .. I regenerated it,
Hmm .. I regenerated it, edited it, matched it etc. but it keeps on complaining.
I'll try the next version as soon as it is released.
@mikeytown2: Do you use the dev in a production environment?
Did you try re-verifying the
Did you try re-verifying the platform / sites after editing the .htaccess files?
HTH,
JamieT
Both, yes. I just did it
Both, yes.
I just did it again but it doesn't help.
Can I somehow find out, whether Boost or the rules work at all?
You can check a number of
You can check a number of things:
-Check if there is content within the cache directory (these should be .html and .html.tgz files) this will prove out if boost is creating cached pages.
-Check the source code of the page you are viewing - You would need to be logged out of course. If you are viewing the cached page at the very bottom you should have a comment stating the page is the cached version. Try visiting this page once and if it is not cached refresh the page and check again as it should be the cached version the second time round.
I had some issues with the platform not presenting the cached page even though it was being generated and verifying the platform / site fixed the issues - it was almost like the modified .htaccess was not being referenced until after I verified the platform not sure why.
Another thing to check is permissions and ownership of the .htaccess file at root etc.
HTH,
JamieT
Sites managed by aegir will
Sites managed by aegir will not load the .htaccess file in the drupal root.
I found that I had toput the boost rules in in /var/aegir/config/server_my_server/apache/platform.d/my_platform.conf
--
Tom
www.systemseed.com - drupal development. drupal training. drupal support.
With the last few Aegir
With the last few Aegir releases, re-verification is needed because Aegir turns off htaccess but will pull in the rules from it on verification.