Closed Bug 425614 Opened 17 years ago Closed 17 years ago

Make use of Smarty cache

Categories

(support.mozilla.org :: Knowledge Base Software, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: nkoth, Unassigned)

References

Details

I have included a patch that allows selective use of the Smarty cache. The way to make use of it is: 1. to cache a particular page, or to display the cached page instead of a newly generated one: Use $smarty->display("tiki.tpl",cache_id, null, time_to_live); instead of the usual $smarty->display("tiki.tpl"); e.g. $smarty->display("tiki.tpl",$page, null, 600); 2. to check if a page is cached: "if ($smarty->is_cached('tiki.tpl', cache_id)) ...." This can then be used to simply display the cached page and to bypass any other processing. Note that in order for this to work correctly for pages that are implementing theme control (i.e. not mozkb.css), this check must be done after "include_once('tiki-section_options.php');" 3. to clear the cached page (which would be needed on page updates, etc...) $smarty->clear_cache('tiki.tpl', cache_id); 4. to mark an area within templates as not to be cached, e.g "monitor this page" text, use the {dynamic}content{/dynamic} block. To implement this properly, especially for logged in users, there will be a need to use clear_cache in many situations. We need a full list of such situations.
Might want to implement a memcache wrapper instead of Smarty. Will be a bigger win.
Priority: -- → P1
Summary: Make use of Smarty cache → Make use of Smarty cache (or memcache page wrapper)
We can do both. Deleting the memcache reference from this bug in favor of bug 395271 which is a dupe of that part. Smarty caching is lower priority.
Priority: P1 → P2
Summary: Make use of Smarty cache (or memcache page wrapper) → Make use of Smarty cache
Target Milestone: 0.6 → 0.7
morgamic says the smarty cache isn't that great.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
Priority: P2 → --
Target Milestone: 0.7 → ---
You need to log in before you can comment on or make changes to this bug.