Possible Bug: Base Folder XML not included with siblings option
I noticed that the Base Folder XML was not included when I
selected the "Start at the current page with folder hierarchy, and
also include siblings" option on a Folder Index. It is also absent
with the "Start at the current page with folder hierarchy,
siblings, and also render forward" option. The "Start at the
current page and include its folder hierarchy" option includes Base
Folder XML.
Is this correct? Are the option descriptions at http://www.hannonhill.com/kb/Block/
correct?
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Tim on 18 Apr, 2014 07:25 PM
Hi,
Thanks for the report. This sounds similar to this known bug which has been around for quite some time. It sounds like you are saying that the 4th option mentioned there is also affected. Can you confirm?
As you can probably imagine, this is a very difficult issue for us to fix because doing so would potentially break implementations across the board as we have no idea how folks have written their Formats. This is the main reason that the bug has been around for so long.
2 Posted by c-siems on 18 Apr, 2014 07:40 PM
It appears to be the same bug, and yes 4th option acts like 3rd option - no Base Folder XML.
I noticed it when I wrote XSLT for a 2nd option Block then had to change to a 3rd option Block because I needed sibling information - poof - Base Folder (1st system-folder tag) wasn't there.
Support Staff 3 Posted by Tim on 18 Apr, 2014 07:47 PM
Thanks for confirming. I went ahead and updated the description of that issue to include mention of that 4th option as well. Feel free to track that issue to see if/when it gets corrected. My gut feeling, however, tells me that this may never be addressed simply due to the likelihood of the fix causing a lot more damage to existing implementations. Let me know if you have any further questions.
Thanks
4 Posted by Lee Roberson (F... on 27 Apr, 2014 04:28 AM
I brought this up over five years ago and it has not changed :)
Because we rely on this behavior I would be remiss if I didn't add my voice to the pile and say that unless there was a switch that changed the rendering behavior that we could turn on or leave off in a future version, there's no way it would work for most customers I know of. I have 600+ sites out there. Even if there was a way to test the waters on this it would approach impossible to find the time to test that many different sites and formats and rewrite things to adjust.
One thing I have relied on heavily time and time again is the presence of the base folder and its metadata in that specific rendering mode mentioned. I doubt that's an issue though since moving toward consistency would probably make the base folder present in more places rather than fewer places.
Support Staff 5 Posted by Tim on 29 Apr, 2014 02:38 PM
Thanks for the feedback, Lee! I'm going to go ahead and close this discussion, but anyone who wishes to track the related issue can do so here.
Tim closed this discussion on 29 Apr, 2014 02:38 PM.