- Install a fresh Drupal 7.
- Add a custom theme, such as one generated by drupalgardens.com
- See how many of your blocks appear on the top of the page (expected that the first block region is choosen for blocks in regions not present in the now enabled theme)
- Go to blocks admin and see how there is no option whatsoever to reposition these blocks
The reason this happens is that the theme defines regions from top to bottom and starts off with 'page_top'. Since Drupal itself defines 'page_top' as a hidden region, it will not show up on the blocks admin page. Therefore blocks assigned to this region are not capable of being administered. This is all fine though. The issue is that blocks should not be put there by Drupal itself, and the root cause is that Drupal will select the first defined block region, despite it possibly being disabled. The solution is very simple, attached.
Comment | File | Size | Author |
---|---|---|---|
hidden-default-region.patch | 678 bytes | Gábor Hojtsy | |
Comments
Comment #1
Gábor HojtsyMarking this critical due to usual practice of listing theme regions from top to bottom on the page as well as seeing some people struggle with this and only being able to resort to SQL trickery, since no UI way can fix this in Drupal by design.
Comment #2
catchComment #3
Dries CreditAttribution: Dries commentedCommitted. Thanks.