Forums / Developer / Cache-block: ezwebin install works, manual install doesn't?

Cache-block: ezwebin install works, manual install doesn't?

Author Message

Jeroen van Duffelen

Wednesday 21 October 2009 12:15:28 am

I'm using a dummy template-set to test if the cache-blocks are working on my manual installation.

The code for this pagelayout.tpl:

<div >dynamic: {currentdate()|datetime('custom', '%Y-%m-%d %H:%i:%s')}</div>
{cache-block subtree_expiry = 52}
   <div >cache block node 52: {currentdate()|datetime('custom', '%Y-%m-%d %H:%i:%s')}</div>
{/cache-block}
{$module_result.content}

The code for the module_result templates (the view cache):

<div >view cache: {currentdate()|datetime('custom', '%Y-%m-%d %H:%i:%s')}</div>

When viewing this dummy template-set on a standard installation of ezwebin (auto installation with install interface), the cache-block gets cleared when editing the node with ID 52. When I view this template-set on my manual installation after editing... the cache block doesn't clear. Everything runs on the same server with the same server settings. So that can not be the problem. So I'm wondering what could cause my broken cache-blocks?

Are there ez pubslish settings (smart view cache clearing maybe?) wich make the cache blocks work in ezwebin and not in mine? I can't find them :s

Also with the ezwebin install, i can manually clear the cache blocks in the setup interface. With my manual install i can not, the check boxes are disabled.

André R.

Thursday 22 October 2009 12:54:49 am

Difficult to answer, but have you compared the site.ini files of the different siteaccesses?
If they are grayed out, that usually means that cache type is disabled in the current siteaccess.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Jeroen van Duffelen

Thursday 22 October 2009 4:09:18 am

Found it...

It seems that you have to enable
TemplateCache=enabled
TemplateCompile=enabled

On both the front- and the back-end. I had them switched of at the backend whole the time!

Thx again André!