devel:caching
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
devel:caching [2013-10-06 04:55] – [Images] Small grammar correction. 58.6.174.67 | devel:caching [2023-09-02 16:31] (current) – Klap-in | ||
---|---|---|---|
Line 7: | Line 7: | ||
http:// | http:// | ||
+ | |||
+ | Some of your URL might look like this ''? | ||
+ | |||
+ | http:// | ||
+ | http:// | ||
To force recaching of all pages, including page instructions, | To force recaching of all pages, including page instructions, | ||
Line 12: | Line 17: | ||
To only force recaching of page xhtml, touch '' | To only force recaching of page xhtml, touch '' | ||
- | To purge the editor toolbar (an other cached JavaScript) call | + | To purge the editor toolbar (and other cached JavaScript) call |
http:// | http:// | ||
- | and clean up your browser' | + | and clean up your browser' |
+ | |||
+ | You can also clear the CSS cache in the same way: | ||
+ | http:// | ||
===== Two-Stage-Caching ===== | ===== Two-Stage-Caching ===== | ||
Line 20: | Line 28: | ||
DokuWiki uses two cache files per page. To understand this you need to know that a page is parsed to an intermediate instruction format first before it is rendered to XHTML. DokuWiki caches both -- the instructions and the rendered XHTML. | DokuWiki uses two cache files per page. To understand this you need to know that a page is parsed to an intermediate instruction format first before it is rendered to XHTML. DokuWiki caches both -- the instructions and the rendered XHTML. | ||
- | * __Instruction Cache__ \\ The instruction cachefile only gets updated when the page, the config files(('' | + | * __Instruction Cache__ \\ The instruction cachefile only gets updated when the page, the config files(('' |
* __%%XHTML%% Cache__ \\ The XHTML cache is also affected by a maximum cache age setting ([[: | * __%%XHTML%% Cache__ \\ The XHTML cache is also affected by a maximum cache age setting ([[: | ||
Line 45: | Line 53: | ||
- | ==== developer | + | ==== Developer |
- | A simple measure to avoid caching is that plugin developers turn off caching completely. This is discouraged due to the extra rendering activities, in particular adversely for high traffic wikis. | + | A simple measure to avoid caching is that plugin developers turn off caching completely. This is discouraged due to the extra rendering activities, in particular adversely for high traffic wikis. |
* save some information relating to the pages it's involved with and the dependency specific to each of those pages. | * save some information relating to the pages it's involved with and the dependency specific to each of those pages. | ||
- | * add an [[action_plugin]] component to handle the '' | + | * add an [[action plugin]] component to handle the '' |
- | Caching itself is handled by the cache object(('' | + | Caching itself is handled by the Cache object(('' |
* the '' | * the '' | ||
* '' | * '' | ||
* '' | * '' | ||
- | * '' | + | * '' |
- | * the cache name, '' | + | * the cache name, '' |
=== Individual Page Cache Expiry === | === Individual Page Cache Expiry === | ||
Line 63: | Line 71: | ||
/* code to expire the cached xhtml of page ns:page | /* code to expire the cached xhtml of page ns:page | ||
* $id = ' | * $id = ' | ||
- | * $data = array(' | + | * $data = array(' |
- | * $render = false; | + | * $render = false; |
- | * $persistent = false; | + | * $persistent = false; // this change doesn' |
+ | | ||
*/ | */ | ||
p_set_metadata($id, | p_set_metadata($id, | ||
</ | </ | ||
- | ===== Purge cache button ===== | ||
- | |||
- | In the default theme I tend to add a button for end users to purge cache if they want to. Edit '' | ||
- | <div class=" | ||
- | <?php tpl_button(' | ||
- | <?php tpl_button(' | ||
- | <?php print html_btn(' | ||
- | </ |
devel/caching.1381028156.txt.gz · Last modified: 2013-10-06 04:55 by 58.6.174.67