ZF-3644: Zend_Cache_Frontend_Class does not recognize setOption() after being instanciated

Issue Type: Bug Created: 2008-07-14T16:00:07.000+0000 Last Updated: 2008-09-02T10:39:35.000+0000 Status: Resolved Fix version(s): - 1.6.0 (02/Sep/08)

Reporter: Lars Strojny (lars) Assignee: Fabien MARTY (fab) Tags: - Zend_Cache

Related issues: Attachments:


After Zend_Cache_Frontend_Class was instanciated once, it does not recognize if an option is changed with setOption(). Say I set the cached cached_entity to $instance and set it to $another_instance later on, the behaviour won't change. The problem with it is, that the values of _specificOptions is pulled into local values in the constructor and never read again.


Posted by Fabien MARTY (fab) on 2008-07-18T16:02:09.000+0000


Posted by Fabien MARTY (fab) on 2008-07-18T16:22:34.000+0000

fixed in SVN trunk (thanks)

Posted by Wil Sinclair (wil) on 2008-09-02T10:39:35.000+0000

Updating for the 1.6.0 release.

Have you found an issue?

See the Overview section for more details.


© 2006-2018 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.