@Pádraic Brady Thanks for the fix!

Regards,
Saša Stamenković


On Thu, Feb 4, 2010 at 2:46 PM, Pádraic Brady <[email protected]>wrote:

> Here's a workaround for getting an infinite lifetime, can be called in any
> controller:
>
> // workaround since config cannot define a NULL value :(
>         $this->_helper->getHelper('Cache')->setTemplateOptions(
>             'twitter', // your cache name here
>             array('frontend'=>array('options'=>array('lifetime'=>null)))
>         );
>
>
> Pádraic Brady
>
> http://blog.astrumfutura.com
> http://www.survivethedeepend.com
> OpenID Europe Foundation Irish Representative<http://www.openideurope.eu/>
>
>
> ------------------------------
> *From:* Vladas Diržys <[email protected]>
> *To:* [email protected]
> *Sent:* Wed, February 3, 2010 4:19:54 PM
> *Subject:* Re: [fw-general] Unable to set infinite lifetime with cache
> manager
>
> Zend_Cache_Core::load() Second parameter enables you to ignore validity
> testing:
>
> $cache->load('my_object', true); //should not test expiration
>
> More info:
> http://framework.zend.com/apidoc/1.10/Zend_Cache/Zend_Cache_Core.html#load
>
> --
> Pagarbiai,
> Vladas Diržys
> Tel.: +370 620 69020
> www.dirzys.com
>
>
> On Wed, Feb 3, 2010 at 16:02, umpirsky <[email protected]> wrote:
>
>>
>> Hi.
>>
>> I have in my config:
>>
>> resources.cachemanager.file.frontend.name = Core
>> resources.cachemanager.file.frontend.options.lifetime = null
>> resources.cachemanager.file.frontend.options.automatic_serialization =
>> true
>> resources.cachemanager.file.backend.name = File
>> resources.cachemanager.file.backend.options.cache_dir = APPLICATION_PATH
>> "/../data/cache"
>>
>> In order to have default lifetime set to null (forever). But looks like
>> it's
>> not possible from config file.
>>
>> Am I right?
>>
>> Regards,
>> Sasa Stamenkovic.
>> --
>> View this message in context:
>> http://n4.nabble.com/Unable-to-set-infinite-lifetime-with-cache-manager-tp1461182p1461182.html
>> Sent from the Zend Framework mailing list archive at Nabble.com.
>>
>
>

Reply via email to