Fredrik, I just finished working around the same issue. There was no easy solution. I couldn't get velocity to stop caching even changing the velocity properties. One workaround that was suggested on this list was to reference the css file outside of roller while you're working on it. I did restarted Tomcat for every velocity change, which worked 95% of the time. Occasionally, I needed to clear the specific roller folder inside of the tomcat work directory. And of course, set firefox to 0 cache...but occasionally still had to CTRL+F5 firefox.
I've worked with velocity/tomcat before and never had these issues. Grind it out! Dehru ----- Original Message ----- From: "Fredrik Jonson" <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, October 25, 2007 7:34:38 AM (GMT-0700) America/Denver Subject: How does the cache work? (how do I flush cache globally) Hi, Roller's cache system is a bit too magical for me to grasp, could someone point me to any documentation? Specifically I edit the themes (ccs & velocity files) directly in the webapp folder on disk, and sometimes find that the changes I make wont be reflected in my browser. Not even a restart of the tomcat server will make my changes visible. I'm guessing the cache is on disk (somewhere, where?) and that I need to go in and "Flush cache" on every blog to make the changes visible. Is there someway I can flush the cache globally for all blogs? cheers -- Fredrik Jonson
