Greetings,
When choosing "Disable Drupal blocks/regions" from the Panels "Advanced Settings", the theme I am using, Simply Modern, does not turn off the blocks/regions (the panel layout is only applied to the content area of the page).
I've tested the above Panels page in another theme (the four seasons theme) and it correctly displays the Panels page (removing the blocks/regions from the Panels page).
This is a theme issue but I wanted to see if anyone has come across this, an if so, what the workaround is. The theme Simply Modern uses the Theme Settings API module, maybe that is the source of the problem?
Thanks in advance for any insight you can lend in this,
Scott
Comments
Comment #1
brisath commentedThere seems to be the same problem using the Artist C01 theme. I too am interested in a workaround. If I can have specific code instructions for what I can change in one of the theme files, I'm game.
Comment #2
esmerel commentedThere's nothing Panels really can do to fix this. It's up to the way the theme does or does not check the 'ignore flag' - some themes may just ignore the stock regions, and since you can add other regions in panels.. well. The theme needs to be smart enough to check and ignore other regions during preprocess.
Comment #3
merlinofchaos commentedAccording to this code: http://api.drupal.org/api/function/template_preprocess_page/head
Drupal only 'ignores blocks' if they are in the 'left' or 'right' sidebars.
Themes should be polite enough in their own preprocess functions to not render other regions that might qualify, but they have to do that themselves.
Comment #4
brisath commentedCan anyone provide some instructions for simple code changes (the 'ignore' flag spoken of) that can be applied to a dumb theme, one that has been abandoned by the creators and already modified several times by me? Thanks.
Comment #5
esmerel commentedYou would probably be best off asking this question in the theming forums - this is not a panels issue
Comment #6
scott859 commentedThanks all, for your comments and insight into this. I had posted the same question in the Simply Modern issues and received a reply that indicated a solution that worked for someone else that was having the same problem: http://drupal.org/node/467252
I hadn't yet tried it, but it may offer a workaround for what is going on.
Thanks again,
Scott