Is it recommended to change any of the default settings under System |System Settings |caching ?
Just general practices for a newbie trying to develop templates, not cache changes for when the site has traffic.
Generally I might not want anything wouldn’t want anything to cache that might not show a recent change to a template or template variable. There is no live site.
I realize I can use the Clear Cache control under Site |Clear Cache... but for not just turning off any cache settings that could be a problem would speed site development.
Thanks for any suggestions.
MODx Revo 2.1 and done!
Hi,
That’s a very interesting idea.
You’ve hit on one of my pet peeves. I run into something like that when I use cached Wayfinder calls during testing. (This is done in your template rather than in System Settings) If I add, delete, or change something in the menu, or change my Wayfinder call, I can’t get it to show up anytime soon, which is pretty annoying, and confusing when you start to think that your syntax is off. [And yes, I do forced refreshes and all that]. It’s especially bad when you’re doing something fancy like using a TV for a Wayfinder parameter. So I un-cache my Wayfinder calls during testing. One could say that you do that and then cache the calls for production. However, then later on your client updating the site might experience the same problem, a "change that causes no change". I suppose that you can tell them to clear the site cache, or "wait" awhile. That’s somewhat bogus, but might be OK. I would guess that this varies from host to host, too, and others may have better results.
Another thing would be to have documents be un-cached by default. "Cacheable Default" would be set to "no". The only downside of that would be the need to cache them all before production, just as above. Maybe "Batcher" or something could take care of that?
Geekier cache experts may have better ideas than these.
Cheers
