要强制重新缓存一个单独的页面，只要在 URL 中添加
要强制重新缓存 xhtml 文件，执行 touch
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.
XHTML 和 指令缓存在
data/cache/* 路径下 6)。文件名以
.feed— 为 wiki 生成的所有的 rss 源
<code> ... </code>标签之间的部分
Plugins can now influence cache use via the
PARSER_CACHE_USE event. This allows plugins which introduce additional dependencies for specific pages to check those dependencies and force DokuWiki to refresh the page when it wouldn't normally.
Up until now plugin developers have only been able to turn off caching completely. This has been necessary for plugins like discussion & include. To make use of the new functionality a syntax plugin will need to:
p_set_metadata()functions. If using metadata please try to stick to Dublin Core Metadata standards.
Caching itself is handled by the cache object7). The key parts of that object of interest to plugins are:
dependsarray — DokuWiki fills this all the known dependencies of the page and then uses standard routines to process them. Plugins can add/modify these dependencies before they are processed. The different types of dependencies are:
purge— expire the cache
age— expire the cache if its older than age
files— expire the cache if it is older than any of the files in this array. Only local files may be added.
cache— a unique identifier under which the cache is stored. Normally it is dependent on the page name,
HTTP_HOSTand the server port. Plugins can generate more complex identifiers, e.g. the include generates identifiers using included page names and whether or not the current user has read access to those pages.