Quote:
by the way what kind of problem does uncached templates gives? increase server load?
|
Each vb3 page is getting all "cached" templates in a batch, in one SQL query. Every uncached template needs separate query to run, thus increasing load on SQL server.
To find out what templates are uncached, one have to run the script in debug mode. Of course tt could be done simply by putting $debug=1; at the beginning of the script, but you don't want to scare your users, do you?
So you can install one of the following hacks to restrict debug mode to certain users/groups/IPs:
https://vborg.vbsupport.ru/showthread.php?t=59605
https://vborg.vbsupport.ru/showthread.php?t=61242
After installation, you'll have a table of template usage at the bottom of debugged page, with uncached templates highlighted.
To cache template simply edit debugged script and add template name to globaltemplates array which is usually defined at the very top of the script.