Hi<br>I think the problem here is not in {dynamic} or in {include}, I think the plugin object doesn't reach to the template because it's cached so if you can assign plugin object to smarty before you check if the page is cached it will work.
<br><br>regards,<br> Ahmad<br><br><div><span class="gmail_quote">On 5/3/07, <b class="gmail_sendername">Jon Daley</b> <<a href="mailto:plogworld@jon.limedaley.com">plogworld@jon.limedaley.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Yes, I agree, except that the plugins like blogstatistics,<br>authentication and google haven't worked since we added the template<br>cache, so we did lose useful functionality.<br> Authentication has now been implemented in the core, but I like
<br>both the blogstatistics and google plugins, and wish there was a way to<br>make it work.<br> Using the {insert} tag would be an acceptable solution to me, and<br>it might be possible to get that to work both to optimize the load for
<br>cached pages, and only incur the overhead was processing the extra<br>inserted templates.<br><br><br>On Wed, 2 May 2007, Oscar Renalias wrote:<br><br>> Well yeah it's not that getting plugins to run within cached pages
<br>> was technically impossible... With a little bit of code here and<br>> there everything's possible :) But we never really had a need to get<br>> plugins to run in a cached pages, or else we're kind of defeating the
<br>> point of caching. If there's something that we're not able to cache,<br>> we're still incurring in some extra overhead, as Smarty needs to<br>> process and render a small bit of a template.<br>>
<br>> We can of course make the changes to get around this limitation but I<br>> see two issues:<br>><br>> 1) we wouldn't be able to do it before 1.3, because we shouldn't<br>> break/change the standard behaviour of plugins and the whole plugin
<br>> framework this late into the 1.2.x branch.<br>><br>> 2) and most important, I have been thinking about ways to optimize<br>> cached pages even more. Right now we still need to load the whole<br>> framework in order to display a page that has already been generated
<br>> and for which we don't need any extra classes or processing: we just<br>> need to load the cached version from disk and push it to the client.<br>> Ideally all we would need to do is come up with a way to quickly
<br>> identify if a page is cached (maybe we can use a hash of the URL?)<br>> and quickly send it back to the client, but I need to have a closer<br>> look at the code and see if this is even feasible to do...<br>
><br>> Number 2 obviously means that plugins wouldn't work in cached pages<br>> and this time there wouldn't even a workaround available.<br>><br>> On 2 May 2007, at 17:26, Jon Daley wrote:<br>><br>
>> <a href="http://bugs.lifetype.net/view.php?id=293">http://bugs.lifetype.net/view.php?id=293</a><br>>><br>>> We have talked about this a long time ago, and came up with the<br>>> conclusion<br>>> that plugins can't work inside the {dynamic} tag. It turns out that
<br>>> isn't<br>>> really true.<br>>><br>>> The problem is in class/view/blogview.class.php, where a bunch of<br>>> template<br>>> objects are only included if the template isn't cached. If you
<br>>> move the<br>>> plugin for loop (or the $now) code, those variables are available<br>>> inside a<br>>> {dynamic} tag.<br>>><br>>> However, since that increases the RAM used for cached pages, we
<br>>> don't want<br>>> to just put everything outside the if(!cached) block.<br>>><br>>> I was wondering about either letting the plugins decide themselves<br>>> if they<br>>> should be loaded or not, or check the template to see if there is a
<br>>> {dynamic} tag or have an administration preference that says "Allow<br>>> plugins inside dynamic tags. I am not sure what would be the<br>>> easiest or<br>>> best. Any thoughts?<br>>>
<br>>> I see now that for the plugins the objects are already loaded even<br>>> in a<br>>> cached view (I think) but the call to PluginManager->getPlugins calls<br>>> register() for each plugin in the non-cached view as opposed to the
<br>>> cached<br>>> view. Maybe that overhead isn't that much?<br>>><br>>><br>>> _______________________________________________<br>>> pLog-svn mailing list<br>>> <a href="mailto:pLog-svn@devel.lifetype.net">
pLog-svn@devel.lifetype.net</a><br>>> <a href="http://limedaley.com/mailman/listinfo/plog-svn">http://limedaley.com/mailman/listinfo/plog-svn</a><br>>><br>><br>> _______________________________________________
<br>> pLog-svn mailing list<br>> <a href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</a><br>> <a href="http://limedaley.com/mailman/listinfo/plog-svn">http://limedaley.com/mailman/listinfo/plog-svn
</a><br>><br><br>--<br>Jon Daley<br><a href="http://jon.limedaley.com/">http://jon.limedaley.com/</a><br><br>If animals weren't created to be eaten,<br> why are they made out of meat?!<br>_______________________________________________
<br>pLog-svn mailing list<br><a href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</a><br><a href="http://limedaley.com/mailman/listinfo/plog-svn">http://limedaley.com/mailman/listinfo/plog-svn</a><br></blockquote>
</div><br>