Forums / Developer / More information about cache in debug output
Eirik Alfstad Johansen
Wednesday 05 January 2011 5:42:26 am
Hi,
We have a site where the cache files of specific pages seem to expire without there being any logical reason for them to do so. However, debugging this issue is not an easy one as it requires me to know, for any given URI I visit:
* If there exists template cache files that will be used and, is so, for which templates
Is there any way to get more detailed information about the cache engine (specifically the template cache) and how it behaves within a given view? The info in eZ debug is pretty scarce, and I haven't managed to locate any INI settings which will allow me to get more details.
Thanks in advance !
Sincerely, Eirik Alfstad Johansen http://www.netmaking.no/
Nicolas Pastorino
Wednesday 05 January 2011 6:17:03 am
Hi Eirik !
Happy new year ;)
Have you tried enabling conditional debug output :
[DebugSettings] ConditionDebug=enabled [GeneralCondition] kernel-content-view-cache=enabled eztemplate-tree-cache=enabled
Let us know how things go,Cheers,
-- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye
Wednesday 05 January 2011 7:06:52 am
Hi Nicolas, and a happy new year to you as well!
I tried this, but I'm not sure what to look for. How will this setting affect the debug output?
I took a look at the docs, but they weren't all that helpful in this regard.
Wednesday 05 January 2011 9:14:51 am
Hei igjen,
Through an example : with
kernel-content-view-cache=enabled
and the main Conditional Debug switch enabled, all lines like :
eZDebugSetting::writeDebug( 'kernel-content-view-cache', 'cache expired #1' );
will output something in the main DebugOutput ('cache expired #1' in this case), in a block having a title containing 'kernel-content-view-cache', easily searchable in a browser.
Scanning the default debug.ini, i only found the two debug-conditions pasted earlier potentially matching your needs. However, i do not know for sure that conditional debug statements are located in relevant places for your issue.
Cheers !