1

My drupal 7 site has Boost module (7.1.beta1, the version previous to the current release) installed and I didn't change any settings from the stock install. I saved the settings configuration with the <front> exception, generated the htaccess code, added it to my root htaccess file, turned Drupal core cache for anonymous users off... Everything works, ie, pages get cached to the boost cache directory and anonymous browsing is served from the boost cache. Only problem is that the front page is being cached even when my boost setting exception using the default <front> should be preventing the front page from being cached. I apologize if this is a redundant thread,I searched but mostly people have the opposite problem (ie, they want the front page cached-whereas I don't). I've also cleared the cache via /performance tab after enabling it and made sure there wasn't a boost cache for the front page .

Does anyone know why the boost exception setting isn't working for the front page? Is there perhaps another way to hack boost for this one page to not be 'boosted'? Thanks.

Improve this question
6
  • How does your exception look? Do you use <front>?
    – Volker
    Jan 15, 2013 at 20:41
  • Yeah its the only thing in the exceptions text area.
    – mfink
    Jan 15, 2013 at 20:58
  • The only thing i can imagine from my experience is that maybe there's still the frontpage-html files in the boost-cache folder. Other than that, i have no more suggestions...
    – Volker
    Jan 15, 2013 at 21:03
  • Yeah, I cleared that boost cache folder and it just keeps regenerating back. Thanks for your suggestions, appreciate your help.
    – mfink
    Jan 15, 2013 at 21:05
  • Just a note, but as the front page is most often hit, it's usually the one you want to ensure is cached / served rapidly.
    – David Thomas
    Jan 15, 2013 at 23:15

1 Answer 1

Reset to default
1

What is the actual url of your front page? If your frontpage is the default ( /node ) then you need to add both 'node' and '' to your exceptions list. Boost treats them differently and keeps a copy of each page in the cache.

You can inspect the cache files that boost creates (these are actually plain html files) in the cache apache root folder.

Improve this answer
2
  • Thank you, Mike! The site's url is www.example.com, which is why i thought the default front exception would do it. After looking at site-information it appears that it wasn't that simple.. the url turned out to be www.example.com/3columns#. So I went back to boost, left the front default and added "3columns" to the list and sure enough, it doesn't get cached. Much Appreciated!
    – mfink
    Jan 15, 2013 at 23:45
  • I appreciate that information as well! thx...
    – Volker
    Jan 16, 2013 at 12:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.