We recently upgraded our environment from 1.28 to 1.35 and have seen many of our components start to fail where they were using cache_self. One of the config changes we made in this process was to set autoflush to on as opposed to off like it was prior to upgrade. We are able to get these components to work again by calling $m->autoflush(0) right before cache_self.
Description of what we are seeing: when the component is called for the first time (or with an expired cache) it works just fine. however once the cache is created the component is returning an empty result. Deeper investigation into the cache tree show that a cache file is indeed being created and updated at the appropriate times (i.e. when expire_in is reached) but the only contents in the cache files are the metadata used by Cache::Cache; there is no content from the component itself. as i stated earlier, turning autoflushing off fixes this behavior. my rough guess is that the call_self in cache_self is flushing content that should be going to the cache. any thoughts? is this a real bug or could there be something wonky with our setup? thanks for your help. -- William Cox email: [EMAIL PROTECTED] blog: http://my-dimension.com/ music: http://www.last.fm/user/mydimension/ photos: http://flickr.com/photos/mydimension/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
