Active
Project:
Boost
Version:
7.x-1.0
Component:
Caching logic
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
9 Nov 2010 at 17:53 UTC
Updated:
3 Sep 2015 at 19:29 UTC
Jump to comment: Most recent
Comments
Comment #1
drupalninja99 commentedok 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.
Comment #2
drupalninja99 commentedok looks like its the 'page requisites' clearing that breaks boost.
Comment #3
drupalninja99 commentedwhat i am wondering is if i have to rebuild the boost cache whenever a css change is made when aggregation is turned on.
Comment #4
rodrigoqwer commentedFirst 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?
Comment #5
rodrigoqwer commented