Friday 10 September 2004 11:05:12 am

of coarse a clear cache must be triggered when a cron script alters the content, so when for instance a rss feed is processed a publish process occurs, which clears the cache automatically.
Furthermore there is no need for clearing the cache by the mentioned interval.
I hope I am right with that assumption.

-------------------------------------------------------------------------------------------
join #ezpublish on irc.freenode.org

Friday 10 September 2004 4:58:00 pm

Thanks Paul, for your reply. This is also an interessting link concerning to this topic

http://ez.no/ez_publish/documentation/reference/template_functions/miscellaneous/cache_block.

I already read these articles, but isnt there another way instead of defining "{cache-block expiry=0}". I thought of a global variable, the same variable which defines the default interval of two hours. This way I wouldnt have to add in every cache-block the expiry option. I assume that in nested cache-blocks the expiry option will not be inherited.
Also the reason for the default interval still isnt explained regarding to no occuring publish actions during this interval.

-------------------------------------------------------------------------------------------
join #ezpublish on irc.freenode.org

Saturday 11 September 2004 3:17:21 am

Yes, you are right, it shouldnt be that hard to add these cache-blocks in the pagelayout.tpl.
But please explain me, why its not a good idea to add a cache-block around {$module_result.content}, as I have read somewhere here in this forum.
Concerning to the points mentioned above, i would go for this:

{cache-block expiry=0 keys=array($uri_string,$current_user.role_id_list|implode(','))}
  {$module_result.content}
{/cache-block}

It would also be interessting to know how to avoid clearing the whole cache initiated by a new forum entry. A new forum entry should only clear the cache of the page in which the entry is published of course.

-------------------------------------------------------------------------------------------
join #ezpublish on irc.freenode.org

Tuesday 21 September 2004 12:43:15 am

Could someone be so kind and explain why there is a clear cache interval of two hours, which ignores the case that nothing is published?
thanks

-------------------------------------------------------------------------------------------
join #ezpublish on irc.freenode.org

Tuesday 21 September 2004 5:57:00 am

The only cache which has a default timeout of two hours is cache-blocks. This can be overridden using the expire parameter. The cache might have to expire even though nothing has been published. An example would be a template operator pulling information from another source than the eZ publish database.

Another question is of course, should the default be two hours or nothing...?

Ole M.

Senior Software Engineer - Vision with Technology

http://www.visionwt.com
http://www.omh.cc
http://www.twitter.com/omh

eZ Certified Developer
http://ez.no/certification/verify/358441
http://ez.no/certification/verify/272578

Wednesday 22 September 2004 11:07:22 am

Thanks Hans,
$expiry is hardcoded twice in this file, which should be defined in the constructor as a member var. In IRC we figured out a couple of coding failurs. Have a look on this:

http://ez.no/community/bug_reports/undefined_member_variable_in_eztemplatecachefunction_php
http://ez.no/community/bug_reports/undefined_member_variables_in_eztemplateblockfunction_php

-------------------------------------------------------------------------------------------
join #ezpublish on irc.freenode.org