Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Have not investigated why this happens as yet.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | page-top-empty-div-bartik-22nd-August.png | 44.83 KB | Jeff Burnz |
| #1 | 889882_1.patch | 601 bytes | dhrosa |
| system-page-top-empty-div.png | 28.67 KB | Jeff Burnz |
Comments
Comment #1
dhrosa commentedEdited modules/system/region.tpl.php to only print a region if it has content. system_page_alter checks if a region isn't empty before wrapping it, however that content might eventually not be rendered.
Comment #2
alanburke commentedCannot reproduce.
Tested with Toolbar module disabled.
Tested on all core themes.
Any steps to reproduce?
Comment #3
Jeff Burnz commentedDo a standard install and logout.
Fresh update a few hours ago and fresh install.
Comment #4
Jeff Burnz commentedPatch in #1 fixes the issue but begs the question why this happens only for $page_top and not all other regions.
Comment #5
cwgordon7 commentedLooked into this a bit, this happens because toolbar ads some elements to the page top region, but they are not displayed for anonymous users because for them #access = FALSE. So while the render()able array does not look empty, the content once actually rendered is, in fact, empty. This has to be done at the template level because the only safe way to tell if the render()able array is empty is to render it and look at the result, and since we do not want to render the elements twice, we have no choice but to check the result after it is rendered.
Comment #6
dries commentedCommitted to CVS HEAD. Thanks.