Learn about DokuWiki
Learn about DokuWiki
Compatible with DokuWiki
Export your site or a namespace to standalone HTML pages - including images and media. This plugin is capable of creating an Eclipse Plugin help including the ''context.xml''. You can also select the template to which you want to export your content
Download and install the plugin using the Plugin Manager using the URL given above. Refer to Plugins on how to install plugins manually. For detailed information and download instructions see the home page. In addition, please check out the GitHub repository
If any inconveniences or problems occur, please contact the support at tools [at] inetsoftware [dot] de. Please describe the problem as detailed as possible. The Site Export plugin comes with a logging feature and we ask you to send us the log with settings on debug (see the plugins configuration section).
Well I'm not the author of the plugin, but it's really worthwhile getting it work. Especially if you want to make a static snapshot (customer presentation while development of content goes on; secure as plugins are not distributed).
The main aim is to export your pages in static HTML. Pictures are bundled. As far as you don't forget any plugins everything works fine.
Has anyone been able to schedule this to run as an unattended task? Seems like this plugin would be perfect to use to schedule automated backups.
That is possible using the cron function. There is, however, no description yet
Can anyone tell me how this plugin work? I don't see any button to proceed the export function.
To the the page of the namespace to export start, then go to Admin and click “Site export”. On Linux you need to give write access to some files (see message on top when opening “Site export” page).
The search button doesn't work in the exported site.
That's right. The search relies on the PHP backend which is gone once you've exported the site.
“Command unknown: siteexport”. Whats wrong?
Check if you have cleared the JS and CSS cache - and do a hard reload.
Check what the AJAX response from your DokuWiki was when the export page loads (e.g. use Firebug on Firefox)
If you find anything you think is very wrong, contact our support
The export runs fine from the GUI, but I get no file for downloading
This answer may not apply to all reasons of the question, but it is possible, that the php execution time, set in the php.ini is too short for the export-script.
The script takes a long time, depending on how many links there are in your page - and especially for the first request which fetches CSS, JS, raw alternatives of the page and so on.
Please consider to set a higher execution time (default is about 30sec, try something like 2 minutes ).
I get the status message: “Finished but download failed.” and there is no output file created in the filesystem on the server. php max_execution_time is 120s.
Where is the error log file located?
The logfile can be set in the DokuWiki's configuration page section “Siteexport” (see screenshot).
The destination has to be write able by the server and you need to set the debug level to other than “none”.
I'm getting the following error: 'Can't create preload file in 'inc' directory. Template switching is not available. Plugin disabling is not available.'
The site export plugin requires write permissions to the inc/preload.php file in order to provide template switching and plugin disabling functionality
It's best to just create the file inc/preload.php and give write permissions for the web server to it
There is a new Release that is Weatherwax and Binky exclusive. Please check them out.
I try to export multiple pages to pdf format, using the default template
This message appears : Unsupported font type: TrueTypeUnicode (DejaVuSerifCondensed)
Same with only one page.
Doesn't works, have you got an idea ? Thanks ~~Phil
Looks like you're using a Font type in your css that is not supported by DW2pdf - check out the plugin dw2pdf - there should be a help file that shows you how to create that font
The installation of siteexport on DokuWiki Ricewind works really smart. It is great that there is such a useful plugin!
However, the links trouble me: Links within the HTML-copy do not work, they just point to the current HTML page (although the link's title shows the correct page). |
Further, the symbols for external links are gone and most of the template is gone (alsothough “export_body” is not checked).
Please check the settings for excluded directories, by default there are quite a few. Otherwise please get in touch.
In the current version, it seems, there is no setting for excluded directories (or did I just miss the obvious?) - only an input for exclude-regex, which is empty. Nonetheless, the links on my start page all refer to start.html…
I'm getting an error decompressing the downloaded package. It says “the file or the directory doesn't exit”. Could you please upload it again? Thanks in advance.
I heard that a lot. Please check the browser you use. Did you y try copying the url into the plugin-installation from tha admin section? FYI: The tgz has been created using OSX tools.
Unzipper on Ubuntu fails with message:tar: This does not look like a tar archive tar: Skipping to next header tar: Exiting with failure status due to previous errors
Installing via plugin manager seems possible on ubuntu, but i like the possibility to verify packages before installing.
Please check the new Version from GitHib. The Problems should go away :)
The site exports fine but when I open the hmtl, the background images for the template, as well as smiley graphics, don't appear. I notice the html source has references to a lib/images directory which doesn't exist. Any ideas how I can get it to show background images? The images from the media folder show on the pages themselves works fine.~~~~ — gymnophoria 2013/01/27 21:44
The lib/images folder is excluded by default. See configuration.
- What I have to write in Costum Options ?
- And I cant Write anything in the Download destination field.
The Download Fields are readonly so you can copy the URL and start a download from your browser without the Admin-Page (Public sites only).
The Custom Option can be left blank. They only serve the purpose of dynamic stuff if you have PHP enabled or have plugins of your own that need other options.