By zbricoleur on

Up until recently, admin/build/block would show, for each theme, the distribution and configuration of the various blocks, rendered in that theme.

Now, regardless of which theme I click at the top of the admin/build/block page, it shows it in bluemarine. What's worse, it does not show correctly which blocks are enabled for each theme.

The themes themselves, as displayed to the user, are working fine, so I know the block configuration in the database is still OK. What do I need to do to beat the admin/build/block page into submission?

⋅ Categories: Drupal 5.x

Comments

zbricoleur’s picture

zbricoleur commented

Turns out, it wasn't something you could fix from the Web interface. In the account settings for user 1, I had selected a theme (bluemarine). That prevented the block page from displaying correctly; it showed the bluemarine settings for every theme regardless.

Since it's a radio button widget in the My Account page, once you've set a theme, there is no way subsequently to select 'no theme.' So you have to change it by hand in the database. Once I did that, things went back to normal.

benstallings’s picture

benstallings commented

Hi, zbricoleur! Thank you for posting this solution. I'm having the same problem and just tried your solution, but with no success. What value are you putting in the theme column of the user table -- the null string? The string "no theme" as you appear to say above? I tried both, but still the block page displays the same results for every theme.

zbricoleur’s picture

zbricoleur commented

Not null, just an empty string.

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

I just started having the exact same issue, but your fix doesn't help me. =(

None of my users have a theme selected, yet no matter which available theme I select, I only see Garland.

--
http://www.drupaler.co.uk/

--
https://www.codeenigma.com/

mghatiya’s picture

mghatiya commented

I am having the same issue.
As OP hinted, I think it is because I had selected "Administration theme" to be different from the theme I have given to the rest of the site.

What is the right solution in this case, while continuing to have different administration theme?

a_c_m’s picture

a_c_m commented

For what its worth, i found the problem on our site.

A custom module was calling path_to_theme() in a hook_init(), which seemed to force the theme to always be the admin_theme. Putting a wrapper around that query checking if arg(0) !== 'admin' sorted it out.