Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: "All sub namespaces" - Processes totally independent from the chosen parent namespace #95

Open
rgleason opened this issue Aug 22, 2018 · 1 comment

Comments

@rgleason
Copy link

rgleason commented Aug 22, 2018

All sub namespaces just processes all pages below the parent without regard to the namespaces listed on the parent page. In other words, there is no way to limit the pages being included because the procedure appears to simply start at the top page and put all namespaces in the directories below into a list that is processed.

It does not follow namespace links within the document, adding them to a list when the namespace is below the parent, in that way.

Which is also the same situation when we use IndexMenu TOC Table of Contents pages created automatically but without javascript {nojs]. So a TOC page is selected as the Parent and "All sub namespaces" is selected this function is infuriatingly DUMB.

We want to use a single TOC to define the only pages that are to be included in the document!
That is how we always thought this worked!!!

We need a TOC selection in the SiteExport Form, "Export type" dropdown. which will simply add the namespaces in the TOC list to the zip creation list that is processed by the SiteExport.

We also need a way to create [EXCLUDE NAMESPACES] on the same TOC page that permits adding specific namespaces to exclude!!!! The tiny space allocated in the configure area is totally inadequate and may change from export document to export document. This would make a huge difference to ease of use, and reduce endless editing.

These things really must be fixed.

@rgleason rgleason changed the title "All sub namespaces" is Dumb - Processes totally independent from the chosen parent namespace Bug: "All sub namespaces" is Dumb - Processes totally independent from the chosen parent namespace Aug 23, 2018
@rgleason
Copy link
Author

rgleason commented Aug 23, 2018

We really need this improvement to be able to control what is output. It will be an order of magnitude more difficult if we have to manually edit the output document, and we may have to try Epub.

If there is something we can do to help get this improvement, please let us know.

If we have this control, I almost don't care if the "Specify Depth" does not work!!

#94

@rgleason rgleason changed the title Bug: "All sub namespaces" is Dumb - Processes totally independent from the chosen parent namespace Bug: "All sub namespaces" - Processes totally independent from the chosen parent namespace Aug 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant