1. I don't know how to reproduce it.
2. I'm expecting to see my regions defined in mytheme.info, say, on admin/build/block and to see my blocks in my regions on site too.

3.
I've copied prod version of my site to my PC (files and DB dump with "mysql db_name < dump.sql", db_name was created first). Permissions (both filesystem and DB) are OK, all work fine except all my regions are lost with "The block [block_name] was assigned to the invalid region [region_name] and has been disabled" messages on the admin/build/block page. So all my blocks disappeared from site pages too.

I've investigated modules/block/block.module and there is a SQL query near line 235:

$result = db_query("SELECT * FROM {blocks} WHERE theme = '%s'", $theme_key);

where $theme_key contains "garland" which pointed as admin pages theme (by me), but my site uses my own theme and all my regions defined only for my theme. If I manually do that query to DB with my theme name instead of "garland" - I see my blocks with my regions.

Moreover, as I know, admin/build/block should use site theme, not admin pages theme, but I see it in admin pages theme.

Where I get wrong? May be there is some kind of misconfiguration (by me) of what?

Comments

San_ANDREYEV’s picture

Category: support » bug
San_ANDREYEV’s picture

Am I wrong with something here?

exaboy’s picture

I believe you are running into the block bug that has been around since D5. There is a patch for it which im trying to find right now :)

jgsantos’s picture

Version: 6.16 » 6.17

I am having the same problem using Drupal 6.17.

jgsantos’s picture

Priority: Normal » Critical

I am having the same problem using Drupal 6.17.

webthingee’s picture

+1 on this issue

brunorios1’s picture

+1

sydneyshan’s picture

Version: 6.17 » 6.22

Has anyone had a chance to look at this one? More info here: http://drupal.org/node/1215924

brunorios1’s picture

i had a similar problem, and was related to a combination of 4 modules, and i don't which of them.

see more: http://drupal.org/node/1186650

sydneyshan’s picture

Thanks brunorios1 - I have disabled the realname module and the issue has gone away. I'll log a bug on that module's issue queue.

dddave’s picture

Priority: Critical » Normal
Status: Active » Closed (won't fix)

This seems to be a module conflict. If somebody can SHOW that this issue is indeed a core problem, please reactivate otherwise this issue is closed.