I deleted my album's current custom pages sitemap.htt and contents.htt and recreated it.
Contents.htt works perfect as desired independant of the location root path or a folder path.
Sitemap.htt works also almost perfect, only the option 'Show thumbnails' does not show thumbnails if Sitemap.htt is located in a folder (a symbol [X] is displayed instead of a thumbnail). if it is located in the album root thumbnails are shown as expected. The links are OK now in both cases.
In Contents.htt an option 'Include custom pages' is available, this option is not available for Sitemap.htt. Is there any reason for this difference?
Perfect, thank you!
I suppose you haven't officially released this version until now. Please don't forget to modify the note inside sitemap.htt and contents.htt which says in the case of sitemap.htt "The sitemap is automatically generated. Put it in the root of your album!". This is not wrong, but now as the behavior has changed it should say e.g. "The sitemap is automatically generated. Put it in the root of your album if you want that your whole album will be mapped, otherwise in that folder of your album from where the sitemap should be generated,"
From my point of view it is really not a massive demand to add an option for including/excluding custom pages in sitemap.htt, but if you include it in contents.htt (which normally shows also the whole content) why not in sitemap.htt?
I just noticed that it doesn't work correctly anymore if I put a page 'sitemap.htt' in a subfolder of an album. The albums in the subfolder are shown, but the links to the subalbums are missing the name of the subfolder and thus cannot be found.
you asked me, why I want a sitemap in a subfolder. The answer is simple: Sitemap.htt creates a list of albums in original order, while Contents.htt creates an alphabetical index, which is disadvantageous for my large album.
A sitemap is currently created also from a subfolder, only the created links don't work.