I hadn’t messed with any of the cache settings on most of my Revo installs, but I must’ve been browsing through the settings and been persuaded by the description of "Enable Database Cache":
When enabled, objects and raw result sets from SQL queries are cached to significantly reduce database loads.
That sounds great, so evidently I switched that setting from "no" to "yes" and forgot all about it.
Weeks later, I started to get frustrated when my cache wasn’t updating the way I’m normally accustomed to when I would save changes to elements. I’d go back and look and see that the "clear cache on save" box wasn’t checked. "Odd, I don’t remember unchecking that on this snippet", I’d say to myself, and check the box again. Then a few days later I’d go through the same process over again.
Finally today I realized that when I check the "clear cache on save" box, it stays checked as long as I’m editing/saving/editing/saving that element. But if I leave it and come back to it, it will again be unchecked. Every element has the box unchecked the first time you open it.
I turned to the cache area of the system settings, did a line-by-line comparison with another install that wasn’t having this problem, saw that "Enable Database Cache" was set to ’yes’, and thought, "hmm... I vaguely remember doing that". Set it back to ’no’, and my problem went away.
This is mainly an observation and a suggestion. I’d like to propose that in any case where changing a system setting will have a not-completely-intuitive impact on the behavior of core manager functionality, this should be mentioned in the description of the system setting. In this case, lots of headaches would have been averted if, when I’d originally read the description of "Enable Database Cache", it would have read as follows:
When enabled, objects and raw result sets from SQL queries are cached to significantly reduce database loads. (Note: when enabled, the ’clear cache on save’ checkbox on elements will default to unchecked)
☆ A M B ☆
MODX Staff
