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
For detailed information check out the GitHub repository.
/inc/preload.phpfile for template switching
If any inconveniences or problems occur, please file an issue at the bug tracker.
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 long as you don't forget (to install) 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
I get the message “Finished Download” and it appears that it worked (one page is very fast) but there is no download file. Where is it? My config page: http://screencast.com/t/QoWLxLpl1sKk. Can't find log file either.
My problem was Chrome! I just tried it in MSIE and Firefox with no difficulties. The downloaded .zip file was being blocked.
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.
As an experiment I did a quick test on exporting a namespace. This ended up in disabled administrating and error texts of the plugin on top of the wiki. Minutes before I updated to Eleanor of Tsort. Main reason could be my configuration: this is not properly safe: 'Data directory is not secured'-notification (not all permissions are www-data only). Normally no problem in my configuration, but this could mess up things pretty much in combination with this plugin? Cannot reproduce in more detail. If this is the cause, I simply messed things up for myself. If so, forget this and please delete it. Otherwise: be warned.
—- MartinNL 16.09.22
Recent Update of SiteExport caused our Dokuwiki to blank out. By FTP and deleting the siteexport folder under plugins I got the site running again. https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual We use the indexmenu, backup tool, captcha, chkedit, configuration manager, dwedit, extension manager, gallery, info, move, popularity, revert manager, searchindex manager, styling, translation, doku upgrade, user manager, wrap, plus the most normal plugins, like acl manager, plain auth. - Are any of these incompatible? Should I try re-installation? Do you think it was just a glitch in the upgrade? NOTE: The cause of the problem was that both DW2PDF and SiteExport now require PHP 5.6 or greater. We had less. Upgrading fixed the problem.
Rick G. 12/2017
8/22/2018 Comments after installing local servers & siteexport (Bitnami-Doku & DokuwikiStick)
1. The path and filename issues for the se-debug.txt file and the se-html.zip file are very confusing and difficult. See this informative discussion https://github.com/i-net-software/dokuwiki-plugin-siteexport/issues/64#issuecomment-259107715
2. I have found that a single page and the full document (all namespaces) can be created, but the partial (specify level) fails every time. See https://forum.dokuwiki.org/post/62203
3. Also see post 26 for improvements https://forum.dokuwiki.org/post/62204 I am augmenting this post with some improvements that are needed:
4. The good news. Installing the Doku & SiteExport on a local server is definitely faster and more reliable. It was difficult to get it configured however. This needs improvement, can it just be preconfigured in the config file?
5. The other good news is that the SiteExport extension does produce good files for single page and full document, and that when done locally it takes 1/3 the time. With all the major improvements and work done on the Renderer xhtml, ckgedit and dw2pdf I believe the actual conversion process is better than ever. Now we just need some improvements to SiteExport!
We have been using SiteExport for Program Release Documentation for the last 3 years. It has not been easy and has taken a lot of time requiring editing of the resultant html. We will continue to use it but are looking at epub as another good form of publication. I expect that flat html will continue to be used with OpenCPN documentation as all OS have that. Therefore improvements in SiteExport would be most welcome!
I just completed an full document export of 645 pages (many blank pages for indexmenu that are excluded) of all 4 books for opencpn https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn and the file is 160mb, and took about 45 minutes.
I have seen during processing, in the data/media directory, the activity of new zip files being added to a main zip file, as shown by the debug-info file recorded, where each page creates a new zip, then is added to a main zip, then it is deleted in a lengthy serial process, page by page.
Rick G. 8/22/2018
Unfortunately the plugin has some real problems that make it an incomplete solution:
Rick G. 8/23/2018
Mandatory reading for configuration of exports! https://github.com/i-net-software/dokuwiki-plugin-siteexport#dokuwiki-site-export