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

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.

Begin by reproducing the behavior in the SiteExport Form with a TOC selected as the parent, using “All sub namespaces” and an IndexMenu TOC without javascript. Compare the requested TOC selection in the “Export type” dropdown and namespace exclusions against the current export behavior; done means the selected TOC namespaces alone are processed and specified exclusions are honored.

Written by the indexing model from the issue text.