Site Export is an admin plugin that offers a convenient way to download your dokuwiki site as a standalone version. It cycles through your namespaces - a starting point can be given at run-time - and packs the result into a zip file. The result can be unpacked at any place and viewed without having an internet connection. That makes the plugin perfect for providing static documentation to customers on a CD or DVD.

• DokuWiki version Weatherwax, Binky and newer
• You need to log in as administrator to have access to the siteexport plugin
• You have to have the zip compression library of your php installation activated.
• dw2pdf for PDF export options
• a writable /inc/preload.php file for template switching

This is about the Admin --> Configuration Manager page.

• Default Export Depth:
  How far in should the export go. This option will be used when selecting "specific depth" as Export Type.
• Try to export non-public pages:
  SiteExport only allows to export public pages. This option will allow to export non-public pages that the currently logged in user has access too as well. (no yet implemented)
• Wiki Path and name for exported ZIP file:
  DokuWiki namespace and file name that will be used to create temporary files.
• Pattern to exclude resources:
  A regular expression to define paths that should not be exported
• Maximum script execution time:
  Defines an execution time in seconds for how long the script may run while exporting a site via URL Request or wget/curl request. Due to PHP settings this may be very limited and if you export a very large site or namespace the script will time out. This option will take care of redirecting the request as many times as needed until the export is finished for all pages (the time should be long enough to have at least one page exported).
• Debug Level:
  Level of Debug during export job. This may be important to find errors for the support.
• Debug File:
  Where will the debug log be written to? It has to be a writable destination.
• Cache time for export:
  The siteexport uses its own cache timer to determine when an export should be discarded.

SiteExport is only available from the Admin menu at the Additional Plugins section. When starting of from the page you want to export, simply go to the export menu, and hit start.

Basic export options

The namespace/page you actually want to export. This will be predefined with the page you currently visited.

By default this is the same namespace/page that you are going to export. That will result in a flat structure, with the pages at the top level.

You can define a higher namespace which will result in the structure below being exported with potentially empty folders but having the lib (plugins, template) directories beeing at top level.

This is usefull for exporting translated namespaces starting with the root of the translation.

How many pages should be exported?

• This page only:
  Attemps to only export this one page.
• All sub namespaces:
  Exports everything below the defined namespace
• Specific depth:
  Exports everything below the defined namespace but only for the defined depth. The depth means how many namespaces it will go down.

Number of namespaces to go down into.

Will export linked pages outside or even deeper of the defined namespace as well.

Adds the option for renderes to only export the inner body other than exporting the whole page.

Adds all parameters to the links in exported pages - which may make sense when using JavaScript that relies on the links

By default the engine of the DokuWiki. This allows exporting the pages with other renderers, e.g. the siteexport_pdf (derived from dw2pdf) to have pages in PDF file format.

Only available if inc/preload.php is writable.
Allows to export the pages with a different template than the default one.

Only available if the dw2pdf plugin is installed.
Exports the pages into PDF files, one per page. There are options (TOC) to export multiple pages into one large PDF.

Only available if the dw2pdf plugin is installed.
Adds a number to each heading. Usefull for a Table Of Contents inside the PDF.

This is totaly optional.

Allows the creation of context.xml and map.xml files that can be used by Eclipse and its Plugins.

Allows the creation of tox.xml and map.xml files that can be used by Java and the Java Help implementation.

If you do not want the export to be structured like your DokuWiki is, you can create a file called toc in the namespace and create a custom structure that will be used instead.

This is great for having all the chapters of a documentation in their own file and exporting them into PDF as a single file.

See Table Of Contents definition.

The checkboxes stand for each plugin. By checking it the plugin will be disabled temporarily and therefore not generate any CSS or JS output.

This is great for a static export that does not need any other or only some plugins. Be adviced that disabling plugins might improve the speed of PDF export.

Here you can add additional variables that will be given to exported page. This can help to create content dynamically when using other plugins or PHP execution.

Simply hit add Option for a new name / value field, enter the variables name and value. Done.

The three links are convenience links. They will be regenerated by every change of any option. They reflect static URLs that can be copied and used e.g. for ant jobs.

Now: Hit start and your pages will be exported.

Reflects what is currently going on and will display errors that occur during exporting or changing options.

If your configuration directory is writable - which it should after setup, you can save your current setup here.

You can show what has been saved, view them, delete them and re-run them.

If you have CLI access (terminal or whatever) and cron access to your server, you can add the cron.php file to schedule runs of your cron jobs.

If you do not want the export to be structured like your DokuWiki is, you can create a file called toc in the namespace and create a custom structure that will be used instead.

This is great for having all the chapters of a documentation in their own file and exporting them into PDF as a single file.

The structure is basically a list of links:

<toc>
  * [[.:index|Index of the page]]
    * [[.:sub:index|Index of the sub namespace]]
      * [[.:sub:sub:index|Index of the sub/sub namespace]]
    * [[.:sub:page|Page in the sub namespace]]
  * [[.:another-page|Another page]]
    * [[.:another-sub:index|Index of another sub namespace]]
</toc>

The <toc> tag support several options:

You have to define the options like this: <toc notoc merge>

Add a download button for the current page - or any other page

{{siteexport [options]}}

There is the additional syntax: aggregator. This allows an in-page selection of an ordered list of pages in the current namespace and sub-namespaces. Once selected and submitted, that page will be generated with the options provided - and merged back up the list (it actually starts merging top down). (What?!)

The Syntax is (and can be used multiple times per document):

{{siteexportAGGREGATOR [options]}}

• This will actually create a <toc> internally, using the options merge and mergeheader
• Without options it will generate a dropdown-list of all pages in the namespace (except the current) one
• The list will be ordered by a meta key mergecompare which has to be added via the META plugin.
• You can create an element with predefined options using the editor button.
• There are two additional options:
  • exportSelectedVersionOnly - if set it will only export this one selected entry. It will then export this one page with the metadata of the page that has the aggregator.
  • includeSelectedVersion - will export all documents starting from the newest to the document directly prior to the selected one.
  • mergehint=false - disable the addition of merge hints