Closed (fixed)
Project:
Boost
Version:
7.x-1.0-beta2
Component:
Apache integration
Priority:
Minor
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
20 Feb 2013 at 04:28 UTC
Updated:
14 Jul 2015 at 14:33 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedAlmost certainly your front page has a module on it that sets a cookie that then disables boost. Please search the other threads for the names of other modules you have installed as your description has too little information to provide support. If you use firefox and firebug you will probably see after the front page that a cookie DRUPAL_UID has been set, this is set by boost when a login is detected and some modules set the login cookie and so disable boost after the first page. Another thing that can disable boost is a login input box on every page.
Comment #2
Anonymous (not verified) commentedComment #3
aleada commentedDid you use pathauto and non ascii characters in URL s. If yes that is your problem....
Comment #4
anthony.bouch commentedAnother possible cause is the NRAGENT ID set by New Relic. We had advanced New relic PHP monitoring installed on our server until recently. I haven't been able to test this to confirm, but since we removed the New Relic client tracking features, caching of inside pages restarted as expected.
Comment #5
curios commentedHi,
I have similar issue where Boost only works on my frontpage and only on the English version which is the main language.
My site uses i18N and pathauto.
Please kindly share your solutions. Thank you!
Comment #6
sorensong commentedI've disabled pathauto, my url aliases are all ASCII and it's still only caching the front page. Hmm...
Comment #7
sorensong commentedI should say, it's technically caching them (the cached .html files appear in cache/normal/example.com), the problem is they're just not being served. According to the "Last modified" column in my ftp client, everytime I visit any of the non-frontpage pages, it creates a new .html file.
Comment #8
Anonymous (not verified) commentedCan you confirm that your rewrite rules are identical to the rules written by boost and that they are after RewriteBase ?
Also you should be aware that a set of Rewrite Rules (Drupal's standard ones) in a virtual host configuration or even a higher directory like (depending on rewrite inheritance)
read before the boost rules can cause them to be ignored entirely.
Comment #9
sorensong commentedThat was it! Thanks! I had
Before the Boost rules. I put those RewriteCond lines after the Boost code and it worked! Now all of my pages are caching and serving properly. My site is now the fastest Drupal site I've ever had! Awesome thanks!
Comment #10
Anonymous (not verified) commentedNot a problem.
Comment #11
samwillc commented@Philip_Clarke thanks so much! Been hair pulling for the past hour about this, my pages fly now :)
Comment #11.0
samwillc commented2
Comment #12
oemb29 commentedI've used BOOST in 2 Drupal Sites but only work with Front Page, all pages doesn't working because the footer is not being added to HTML Output.
I added the standard code but nothing happen
I can see the cache files into /cache/normal/ directory
Please help me
THX
Comment #13
Anonymous (not verified) commentedcan you post your entire .htaccess file?
Thank you.
Comment #14
oemb29 commentedOk Thanks for your quickly response
This is the .htaccess
Comment #15
Anonymous (not verified) commentedHi, you have boost in the wrong place, it should be before
Comment #16
ashutosh1629 commentedThanks #9 your solution worked for me too!!