Differences

This shows you the differences between two versions of the page.

--- plugin:siteexport [2018-02-20 09:45] – version upped gamma
+++ plugin:siteexport [2023-08-15 06:19] (current) – 2003:c1:5f0e:ca00:4cd6:4bdf:93a9:c3ba
@@ Line 6: / Line 6: @@
 email      : tools@inetsoftware.de
 type       : admin, action
-lastupdate : 2018-02-20
+lastupdate : 2023-07-07
-compatible : Weatherwax, Binky+
+compatible : Jack Jackrum+
 depends    :
 conflicts  : button
@@ Line 39: / Line 39: @@
 If any inconveniences or problems occur, please file an issue at the bug tracker.
 ===== Change Log =====
@@ Line 51: / Line 52: @@
   - install plugin siteexport
   - Get stuff in. This means
-    - config-files like: smileys,... \\ be careful in using everything concerning authentification. In an non-open wiki export doesn't work
+    - config-files like: smileys,... \\ be careful in using everything concerning authentication. In an non-open wiki export doesn't work
     - used templates (I use the default without compatibility problems)
     - hacks of your DokuWiki ;-)
@@ Line 59: / Line 60: @@
   - if you just want to export a branch you have to go to this folder and there enter the admin-area; you can type in the wanted namespace ether. For me it seems to be more safe to view the namespace first!
   - login and go to config-menu: siteexport; check options; to run links to wget and dl-link should appear otherwise it doesn't work
-  - click generate and download the packed pages \\ by starting doku.htm you run the static version
+  - click generate and download the packed pages \\ by starting doku.html you run the static version
-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.
+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.
 ===== FAQ =====
@@ Line 99: / Line 100: @@
 >
-===== Discussion =====
+===== User contributed information =====
-==old javascript api vs jQuery==
+===Processsing large documents===
->>You still use the old javascript api function. Your package has also script_angua.js that's rewritten to jQuery.
->There is a new Release that is Weatherwax and Binky exclusive. Please check them out.
-What is the status on this? because the current released DokuWiki RC version don't support the old javascript api anymore...
-==fonts==
->> 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
-==== Missing links ====
->> 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: <code>tar: This does not look like a tar archive
-tar: Skipping to next header
-tar: Exiting with failure status due to previous errors</code>
-> 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 :)
-==== No template images ====
->> 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.~~~~ --- [[user>gymnophoria|gymnophoria]] //2013/01/27 21:44//
-> The lib/images folder is excluded by default. See configuration.
-==== Error Comand unknown: add option ====
->- 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.
-==== Corrupted ZIP & Other Issues ====
-  * The ZIP archive that is generated is reported as being corrupted by Windows explorer and 7-zip.  Simple attempts to repair it fail.
-  * //preload.php// appears to be populated with generated PHP code - without the starting <?php so the code just ends up being echoed on to every page of the wiki.
-> 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
-==== PHP 5.6 now required ====
-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
-===Processsing large documents===
   * Clean up the document - Use MultiOrphan, Fix orphans and wanted for media, links and namespaces. Use standard images, no animated gifs.
   * Make sure the single page can be created with the plugin, if not, fix it.
@@ Line 173: / Line 112: @@
   * When processing the full document and it fails,  try excluding the page under admin > configuration > siteexport  "exclude" and then run the export again.
   * When the document completes, go back and fix all the excluded pages.
+  * If the document does not complete, consider setting up a mirrored local Dokuwiki server and running SiteExport there. Why? Because your online server may not have enough memory and power to complete the task. We have had to resort to this technique to successfully complete large tasks. It is more effective than stubbornly trying to make it work with an underpowered website.
+===Processsing large documents===
+/22/2018 Comments after installing local servers & siteexport (Bitnami-Doku & DokuwikiStick)
+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
+  * Please see this forum post https://forum.dokuwiki.org/thread/16168  Sometimes the SiteExport Config says only "file" and a path is needed and visa versa.
+  * Also I found that the only way I could get it running was to either remove the path and just have the filename or put in an absolute path.
+  * Having relative paths does not work in this configuration on Windows.
+  * Is there any way the user could "Browse to the file? See the notes in the thread above. Only after getting these paths correct, does the extension work at about 75%. See post 25 https://forum.dokuwiki.org/post/62202
+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?
+  * Is the download connection through the Browser what is causing trouble with the internet version? Maybe there should be a choice to just drop the outcome on the server somewhere, disabling the browser download? --Sort of a workaround? Then maintenance admin can download the file with FTP or something?
+  * It would be very helpful to get SiteExport working better on the internet, or to identify what the bottlenecks actually are on the server or the internet. (It takes ages and ages to complete, why?)
+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.
 ===Github Readme.md file===