Lines Matching refs:a

3 …a convenient way to download your dokuwiki site as a standalone version. It cycles through your na…
4 …tion. That makes the plugin perfect for providing static documentation to customers on a CD or DVD.
14  * a writable <code>/inc/preload.php</code> file for template switching
29 …y run while exporting a site via URL Request or wget/curl request. Due to PHP settings this may be…
33  Where will the debug log be written to? It has to be a writable destination.
49 By default this is the same namespace/page that you are going to export. That will result in a flat…
51 You can define a higher namespace which will result in the structure below being exported with pote…
86 Allows to export the pages with a different template than the default one.
94 Adds a number to each heading. Usefull for a Table Of Contents inside the PDF.
106 …uctured like your DokuWiki is, you can create a file called <code>toc</code> in the namespace and …
108 …is is great for having all the chapters of a documentation in their own file and exporting them in…
115 This is great for a static export that does not need any other or only some plugins. Be adviced tha…
120 Simply hit _add Option_ for a new _name_ / _value_ field, enter the variables name and value. Done.
139 …uctured like your DokuWiki is, you can create a file called <code>toc</code> in the namespace and …
141 …is is great for having all the chapters of a documentation in their own file and exporting them in…
143 The structure is basically a list of links:
165 pagebreak | inserts a pagebreak after each page defined by the namespace
170 Add a download button for the current page - or any other page
185  * This will actually create a `<toc>` internally, using the options `merge` and `mergeheader`
186 …* Without options it will generate a dropdown-list of all pages in the namespace (except the curre…
187  * The list will be ordered by a meta key `mergecompare` which has to be added via the META plugin.