i-net-software / dokuwiki-plugin-siteexport

DokuWiki plugin to export pages or namespaces to static html
https://www.dokuwiki.org/plugin:siteexport
GNU General Public License v2.0
24 stars 12 forks source link

Namespace Confusion for export #72

Closed rgleason closed 7 years ago

rgleason commented 7 years ago
  1. Set Namespace: opencpn:toc <-- OpenCPN User Manual TOC https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:toc flat totally opened TOC created with this code in the page: {{indexmenu>:opencpn:opencpn_user_manual#5|msort nsort nojs}}
  2. Parent Namespace to export: opencpn:opencpn_user_manual
  3. Export Type: All sub namespaces
  4. Export Linked Pages: checked
  5. Export all parameters (eg. "do"): checked
  6. Render Engine: ckgedit
  7. Export Template: bootstrap3
  8. Default Lang: EN
  9. Disable JS Plugins: Check START

It immediately starts "Adding" opencpn:developer_manual ..... opencpn:supplementary_software... opencpn:supplementary_hardware...

Yet those are not in my "Parent namespace to export" !!

rgleason commented 7 years ago

VARIATION -test

  1. Set Namespace: opencpn:toc <-- OpenCPN User Manual TOC https://opencpn.org/wiki/dokuwiki /doku.php?id=opencpn:toc flat totally opened TOC created with this code in the page: {{indexmenu>:opencpn:opencpn_user_manual#5|msort nsort nojs}}
  2. Parent Namespace to export: opencpn:opencpn_user_manual
  3. Export Type: All sub namespaces
  4. Export Linked Pages: NOT checked <-- Of course we want html pages linked, what does this do?
  5. Export all parameters (eg. "do"): NOT checked <-- What does this do? What parameters?
  6. Render Engine: ckgedit
  7. Export Template: bootstrap3
  8. Default Lang: EN
  9. Disable JS Plugins: Check
  10. START

It immediately starts "Adding" opencpn:developer_manual ..... opencpn:supplementary_software... opencpn:supplementary_hardware..

Yet those are not in my "Parent namespace to export" !!

rgleason commented 7 years ago

VARIATION -test

  1. Set Namespace: opencpn:opencpn_user_manual:toc <-- TOC https://opencpn.org/wiki/dokuwiki /doku.php?id=opencpn:opencpn_user_manual:toc flat totally open TOC created with this code in the page: {{indexmenu>:opencpn:opencpn_user_manual#5|msort nsort nojs}}
  2. Parent Namespace to export: opencpn:opencpn_user_manual
  3. Export Type: Specified Depth Depth 3
  4. Export Linked Pages: checked <-- Of course we want html pages linked, what does this do? 5 Export all parameters (eg. "do"): checked <-- What does this do? What parameters? 6 Render Engine: ckgedit
  5. Export Template: bootstrap3
  6. Use TOC in Namespace: Not Checked <---what is this used for?
  7. Empty namespaces in TOC: Not Checked <---what is this used for?
  8. Default Lang: EN
  9. Disable JS Plugins: Check START

It immediately starts "Adding" opencpn:opencpn_user_manual....

Now this is what I intended, but I don't know why the other tests didn't do this?

rgleason commented 7 years ago

Set Namespace: opencpn:opencpn_user_manual:toc <- Point directly to the TOC Page. Set Parent Namespace: opencpn:opencpn_user_manual <- Point directly to the User Manual namespace.

Here is a documentation page for the OpenCPN.org "Books" Indexmenu Plugin showing how to build a TOC page for a namespace that can be used in SiteExport.

https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:edit_user_manual:test_navigation_toc#siteexport_pluginopencpn_user_manual_toc

Here is a documentation page for the OpenCPN.org "Books" SiteExport Plugin showing how to use the TOC page in SiteExport and what configuration settings we use. https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpn:opencpn_user_manual:edit_user_manual:site_export_plugin

There is also information about setting up the debug.txt file in case the plugin is not working.

We are still trying to get it to complete, however.

rgleason commented 7 years ago

We finally got debugging working, but are still working on getting the SiteExport to complete.. See #69 #70 #71 #72 #73. We will be closing this.

The lead developer has an issue he posted. #74