Code: Select all
$smarty->loadCacheResource('apc');
$smarty->setCaching(true);
This is the "Developers Discussion" board (not "Product Support"), therefore I was curious for your thoughts and opinions and a possible hint where to put the 2 lines of code, so I can test it on my behalf.Smarty 3.1.24 has a LONG list of new features, bug fixes and improvements since 3.1.21 (22 and 23 were never released publicly.) Most notably, compiling speed has been improved by 30-40% over the last release!
The libraries included in CMSMS are (with the exception of 3rd party modules in the modules folder that are not part of the installed package) considered as being part of the core, and are maintained as such. The Dev team has tested all the available versions of these libraries, and use only the ones that are considered stable to be used with CMSMS. We also may modify any of those libs to work better with each release of CMSMS. So there are reasons to use one version of a specific lib instead of a more recent one. And by updating any of the libraries by yourself you may be creating bigger problems than the ones you are trying to solve, and that is considered a hack.swgreed wrote:I wasn't aware of "hacking" CMSMS (which implies a rather negative annotation) but keeping a 3rd party module up to date.
According to the changelog, the .24 release would also improve performance (i.e. "quick win").
In practical terms all you need to know is on that topic, and there is no need to hack CMSMS in any way. There are several approaches possible, for instance with an UDT with those 2 lines of code being called by a "ContentPreCompile" event from the CMSMS core... I didn't test it but that should work as long as you add the plugin file to the plugins directory.swgreed wrote:The Smarty thread I mentioned was from 2010 when Smarty 3.0.x was just released. It's not specific to 3.1.16 or 3.1.24. Switching back to Smarty 3.1.16 (to a "non-hacked" state) raises the same question as in posting #1.
