Quote:
Yesterday at 09:52 PM filburt1 said this in Post #2
IMO I think it's a pretty dumb system; a better way (again, IMO) would be to associate each template with one or more PHP files, and then have the template engine automatically cache all necessary templates for that file.
|
In default vb caching system dev has freedom to decide whether he will cache a template or not.
It is not always desired to cache all templates a .php file uses because some of them are used only in certain conditions (like error templates or ignore user templates) and devs may not want to cache these everytime that php file runs. This is because everytime you cache a template you are eating up your server RAM. Sometimes you prefer to save some RAM space, instead of saving an extra query which will be very infrequently added.