fix cache wackiness
We're seeing a lot of support tickets reporting problems that are fixs by clearing the cache. We'll gather examples here until we can find the exact bug(s), ticket more precisely, and squash 'em.
Related support tickets:Relevant user stories:add one
I wonder if it's possible that somehow the new layout functionality is leading to entire pages getting cached? --Ethan
Would that account for included cards that have just been added not showing up when reloading?
--John Abbe.....Wed Mar 30 13:29:23 -0700 2011
(It would, but that didn't turn out to be the issue).
I think we need to make a bigger priority of this. I turned the content caching back on and added a new debugging page: /admin/show_cache/[cardname]. So far I haven't heard any chatter about cache issues. But in general we should try to check the debugging page before clearing the cache.
--Ethan McCutchen.....Thu May 26 17:22:07 -0700 2011
I just added a fix that addressed the example case. Basically I made it so that all of a card's particles (eg, for card A+B+C, particles would include A, B, C, A+B, and A+B+C) have their cache cleared whenever there is a saving error on the card. There may be some more semi-obvious things like that that we're missing. The reproducible example above was highly useful for this!!!
--Ethan McCutchen.....Thu May 26 17:24:34 -0700 2011
moving this to testing because of all the refactoring that we've done (and the lack of reproducible problems to test)
--Ethan McCutchen.....Tue Jul 19 12:05:54 -0700 2011
Closing. I don't really believe we've fixed *all* the cache wackiness, but I don't think we have any reproducible examples of things breaking.
--Ethan McCutchen.....Mon Aug 08 14:43:06 -0700 2011
Notes