To reproduce, set a separate administration theme in admin/settings/admin. Confirm the custom administration theme by visiting other admin pages such as admin/build. To show the bug, visit admin/build/block; the global site theme will be used.

I am not really Drupal-competent yet or I'd include a patch. But here's what I've found: modules/system/system.module correctly sets the $custom_theme global variable to the name of the admin theme at line 1884. But then in block/block.admin.inc (in two different contexts), the $custom_theme variable is set to the existing $theme variable or the default theme, clobbering the "use the admin theme" flag set in system.module.

Surrounding the clobbers with "if (!isset($custom_theme)) {..." works around the problem but probably isn't the definitive solution.

Comments

GSnyder’s picture

GSnyder commented
Status: Active » Closed (fixed)

I didn't file this properly and it never showed up as new - going to mark it closed and resubmit.

prajila.v.p’s picture

prajila.v.p commented

i also have the same problem