Hi - I have two questions please:
1. If you want to remove a sidebar entirely, is the best way (or only way) to do this to assign that region to the "None" zone, effectively making it an unassigned region?
2. Even with "Force this region to be rendered" unchecked I notice that when I am logged in, that empty regions are still being rendered e.g. an empty sidebar is still taking up width (see screenshot1). This is not the case when I am logged out, meaning the sidebar is not rendered (see screenshot2). Is there anyway to be logged in and when a region is empty that it does not get rendered? This would just be nicer for my users.
Thanks for looking
Tim
Comment | File | Size | Author |
---|---|---|---|
screenshot2.jpg | 135.65 KB | timtunbridge | |
screenshot1.jpg | 150.36 KB | timtunbridge |
Comments
Comment #1
Argus CreditAttribution: Argus commentedIf you disable debugging it will not be rendered anymore.
Comment #2
timtunbridge CreditAttribution: timtunbridge commentedThanks for that. Sorted now.
Comment #3
ryanwebpage CreditAttribution: ryanwebpage commentedI am experience the same issue with debugging disabled. While not logged in the regions do not appear if they are empty but if you are logged in they show up. For example sidebar first shows up with the following markup
<a id="context-block-region-sidebar_first" class="context-block-region">Sidebar First</a>
. What ever parsing needs to happen to determine if the regions are empty appears to be ignored if you are logged in. The markup is always generated for regions which in most cases does not have an impact on the layout. However, for sidebars since they float the content region is not where expected.I tried disabling other modules to see if they were conflicting with Omega and was not able to determine the cause. I also thought it might have something to do with contextual links with no luck disabling them either.
Is anyone else experiencing this issue with the stable release? I did a little code diving but was not able to determine where the regions and their grids were being handled.
Comment #4
ecoluke CreditAttribution: ecoluke commentedLooked around for ages to find this - might be worth making that piece of info more readily available / obvious! :)
Comment #5
tombh CreditAttribution: tombh commentedJust been wrestling with this same issue myself. I think it's a broader problem with the way Drupal 'helpfully' displays the outlines of block regions if you're logged in as a role with permission to edit blocks.
Comment #6
Anonymous (not verified) CreditAttribution: Anonymous commentedThis is driving me nuts. :) I disabled all debugging options but the sidebars are still rendered for user 1. I can't for the love of me figure out how to get rid of them. Did anyone find a solution besides removing them? I might need the sidebars on some pages but not on others. Of course, I could use Delta - but that would make things more complicated than they need to be.
Comment #7
lsolesen CreditAttribution: lsolesen commentedExperiencing the same problem - not only for user/1 but also for other administrator users.
Comment #8
3djeff CreditAttribution: 3djeff commentedAre you using the Context module? If so....
By default, in the 'context settings' at /admin/structure/context/settings
the below setting box is checked.
Show all regions
Show all regions including those that are empty. Enable if you are administering your site using the inline editor.
This causes regions to be rendered when logged in as an admin. Unchecking it solved the problem.
Comment #9
lsolesen CreditAttribution: lsolesen commentedI am not using context. I am using panels.
Comment #10
zterry95 CreditAttribution: zterry95 commentedfix it by disable debug.
I am using delta + context.