The big problem it appears is that if you clear all the Drupal cache tables and have aggregation turned on it will change the file name of the CSS/JS aggregated files and so boost is then left with outdated CSS/JS filenames and the page completely breaks which is terrible.

Is there not a way to force boost to clear its cache when the core cache tables are cleared?

Comments

drupalninja99’s picture

ok i found the 'Ignore cache flushing' option. i dont understand why you would want to ignore it at all if you are using aggregation. it seems like you would definitely want it disabled if you're using aggregation bc the cache files are renamed. i have turned it to disabled for now.

drupalninja99’s picture

ok looks like its the 'page requisites' clearing that breaks boost.

drupalninja99’s picture

what i am wondering is if i have to rebuild the boost cache whenever a css change is made when aggregation is turned on.

rodrigoqwer’s picture

Issue summary: View changes

First of all, sorry for my english. I have exactly the same problem. I had checked that with boost module and only JS aggregation enabled (only JS, CSS aggregation doesn't cause any problem) drupal logs me out when I'm navigating my website because it serves boost cached pages. I think the source of my problem could it be what you are saying drupalninja99. When you clear site cache under settings-->performance drupal regenerates JS files and boost doesn't clear caches if you don't disable "Ignore a cache flush command if cron issued the request" and boost keeps old JS aggregated file names. I had disabled this option and all works fine now. But i don't want cache to be flushed everyday (this is how i had configured cron run). I had configured boost to flush pages after 1 week, but cron will flush my cache after 1 day and i don't want cron to be run after 1 week. Do you know how can I do this?

rodrigoqwer’s picture

Version: 6.x-1.18 » 7.x-1.0
Issue tags: +boost, +JS aggregation, +cache, +logged out