restrictions on nestable pages?
I've been working on some new pages and I was attempting to create a consistent header across all of them. However, I noticed a few things:
1) the default Header page has an override that prevents it from being nestable (it will revert false -> true changes in XML view on save, toggle is hidden in Canvas view), which makes it impossible to make a single Header and nest it in each page. The result is constantly having to add all of the header modules to each new page you create, which is highly inefficient.
2) As a workaround, I created a new Page (e.g. Header2) and a new Layout (Header2), assuming that I could make an exact copy of the current header objects with custom content, which would hopefully not be subject to the constraints of #1 above. I can see the 'nestable' toggle now, but the same thing is happening on save- it reverts to 'false'.
It's a bit tedious and likely to cause errors if this replication must occur manually on every page we maintain. I've also noticed that the footer page can be nested, which thoroughly perplexes me, as it's common for a site to have consistently fixed header/footer working in tandem. Is there something I'm missing? I've seen new system pages without the frontend header content, but the page layout has the header sections (without the actual custom modules in the layout, though), so maybe they're added by default somehow?
I did some research on this and I believe I've discovered the bug, I'm filing a ticket to have this fixed. The bug is this:
Certain core pages (such as Footer and Header), are set as "nestable=true" by default, so that they can be embedded in other pages. However, modifying any of these pages in the Page Editor, then saving them, auto-sets "nestable=false", thereby rendering them un-embeddable in other pages.
This is what happened in your case, since Header was edited and saved. For now, if you would like me to fix this for you (directly in the Header asset), send me a PM. Hope this helps!
Sincerely,
Venk
