Closed herbdool closed 2 years ago
Yup, Page title should be suppressed (the one that shows up by default when choosing a template). Is this a matter of telling the layout what the context is?
I did notice this and thought of how page title and tabs could be suppressed, and failed. Problem is that
<?php if ($tabs): ?><nav></nav><?php endif; ?>
layout_preprocess_layout()
runs after any attempted override (its meant to run last and is given a weight to ensure this) and does $variables['tabs'] = menu_local_tabs()
So failing any bright ideas, I suspect we'll need to avoid templates with tabs and titles.
I'll agree that a mini-layout shouldn't be able to embed itself... I noticed this too when testing and thought it was an odd behavior. I can't see any reason why a mini-layout would ever need to add itself and to infinity no-less.
And the block add list isnt alterable.
Maybe this is a need for a new hook in core.
Maybe this module could add a handful of simple layouts to steer someone away from other ones. Is there a way to categorize the layouts?
Could a simple css "display: none" be added for a quick and very dirty workaround?
Found a one-liner trick to hide page components. Still cant prevent adding a block to itself yet. But the code wont let that render anyway.
This doesn't really help with the conversation, its more of an FYI. I added a mini-layout to a mini-layout and it effectively broke the site... I could visit the home page but it wouldn't load any other pages. So, not only should it not be allowed to add itself, it's quite broken if it does.
I added a mini-layout to a mini-layout and it effectively broke the site
Fixed that. Can still add block within block but will not render if you do.
Should a mini layout block be able to embed itself? I see it available in the list. Should "Page title" be suppressed? What about "Main content page"? Maybe that's ok.