Re: [SMARTY-DEV] Bug!? Outputfilters don't work like in previous versions (post-2.5.0-cvs)

On Sat, Apr 26, 2003 at 11:02:04PM +0200, Wom.bat wrote: > Hi folks... > I don't like {insert}s, because they are rather slow, but I needed to > display the number of comments on news. As the news are cached (the > template(s), of course), I used a replacer token (sth like > #replacer-comments-news-id#) and let an outputfilter run over it. hmm. that's quite how inserts work, too. > This always worked perfect until now: it now seems that the output filter > gets cached, too. The display doesn't change after I add a comment, it > remains at the previous value. If I switch force_compile to true, everything > works as usual. Maybe this issue exists since longer ago, I don't know > exactly, as I usually am developing with force_compile to true and so didn't > recognize the bug (is it a bug!?). I'm not exactly sure, but I'd say it > worked with 2.4.x the outputfilter is run *before* the file is written to the cache. so the outputfilter's work is cached too. but this way is not a recent change. i'm pretty sure all 2.4.x work this way, too. > I use one template index.tpl in which I include the rest of the site (php > files, not templates directly) via include_php. all php files are using the > same smarty object. in the php files, I enable or disable caching and then > display the template. > Maybe I'm doing something in the wrong way, if so, please let me know... so you start with caching=false and caching is also false after your "$smarty->display('index.tpl');" returned ? anyway: with caching=true the outputfilter never worked as you expected. greetings messju > Regards, > David