Share » Forums » Developer » [solved] Cache block - Subtree expiry...

[solved] Cache block - Subtree expiry - error.log

[solved] Cache block - Subtree expiry - error.log

Thursday 18 December 2008 4:04:40 am - 4 replies

Modified on Friday 19 December 2008 4:17:03 am by Clemens T

Author Message

Ivo Lukac

Thursday 18 December 2008 5:09:29 am

Hello Clemens,

Your line:

{cache-block subtree_expiry=$uri_string keys=array($uri_string,$current_node.node_id)}

does not make sense.
With subtree_expiry you set in which part of tree published objects will trigger cache expiry.
Also $uri_string and $current_node.node_id carry same information so you don't need it both.
This will do want you want:

{cache-block keys=array($uri_string)}

http://www.linkedin.com/in/ivolukac
http://www.netgen.hr/eng/blog
http://twitter.com/ilukac

Clemens T

Thursday 18 December 2008 6:42:01 am

Thanks Ivo for paying attention to my problem.

The thing is that the menu items are editable, so when I change the title of menu item 1 to menu item 2, the pagelayout should be invalidated. This behaviour should be the same for submenu items.

Is this line then still sufficient?

{cache-block keys=array($uri_string)}

Ivo Lukac

Thursday 18 December 2008 7:30:23 am

Yes. If you don't place subtree_expiry that cache block will expire after publishing objects anywhere in the tree.
Here is more about this: http://ez.no/doc/ez_publish/technical_manual/4_0/reference/template_functions/miscellaneous/cache_block

http://www.linkedin.com/in/ivolukac
http://www.netgen.hr/eng/blog
http://twitter.com/ilukac

Clemens T

Friday 19 December 2008 4:17:33 am

Thanks, that at least saved the subtree_view errors. I'll make another post on the unlinking error.

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu