I'm not a fan of directory chaining, but at least when restricted to sibling directories it produces less confusing navigation. There are users, however, who really do want the chaining to traverse the entire tree.
It would be nice if the user could choose no chaining, sibling chaining, or full tree chaining. To avoid skin breakage, it would need to be implemented as the current isChainDirectories(), but with a new "chain flavor" variable.
Proposed UI attached.
(This started elsewhere, but might get lost in the shuffle.)
BTW, this might also be a good time to fix a longstanding error. If directories are chained, and there is a web location anywhere in the project, and the skin is set not to produce slide pages for web locations, navigation errors occur, with a "next" arrow leading to a slide page that doesn't exist. Try it with Minimal.
ETA: Thread locked to prevent yet another derailment.
Getting closer. But full tree chaining fails completely if there's a webloc as the first or last object in a folder. Zipped sample project attached.
ETA: To be specific, in this test album, if you start with the slides of F1, the chaining doesn't take you to F2. If you start with the slides in F2 and try to use "previous," you get a 404 when you try to go back to F1.
Seems to be fixed in b11, but I'll bet there's some situation still lurking out there....
This is a very old bug, but once I shut off all chaining in my skins, I just stopped worrying about it (and it was never a problem in my lightbox skins, since those automatically ignore weblocs). But having reintroduced chaining in my "slide page" skins, it all came back to me.