I used on my CVS-Testsite a long time one of the default themes.
As I started to write my own one no block was shown.
First I thought it was my fault, then I took a look at /admin/block and saw that all the activated blocks (like Navigation and some other) are not shown in the list.
Then I looked at "bluemarine settings" and there were all this blocks listed regularly.
After this I took a look at the database and I saw the following:

  1. the not listed blocks of this theme have no "region"-value
    (and NO I dont use any other regions as the default one)
  2. there are very many table-rows in the DB. - not just for the few themes also for all modules (customerror,contact,filter,flexinode....)
    the most confusing on this is that the module-name is listed in the theme-field ????
    why are they needed?

has anyone seen the same?
solutions? ideas?

I want also point you also to this error: error on /user/*/edit

Comments

naudefj’s picture

I had the same problem and had to restore back to 4.6.0. Hope it will be fixed soon...

Uwe Hermann’s picture

Yep, I can reproduce this in HEAD. Will take a closer look if I get around to it.

Tobias Maier’s picture

the main issue was fixed in http://drupal.org/node/29506
but there are still the many table rows...

has anyone else seen this?

jakeg’s picture

I'm getting this problem too. I just checked out the latest CVS and I still get it. Perhaps I have to do a mysql update too though?

Tobias Maier’s picture

today I found out that if you enable a theme at admin/themes and then a user changes his theme to this all blocks are never shown.
First I thought it is because of the Forms API update today but I saw the same error on a few das older cvs-version

http://drupal.org/node/29465#comment-48367

killes@www.drop.org’s picture

Is this still an issue?

Tobias Maier’s picture

Status: Active » Fixed

i dont think so...

puregin’s picture

Status: Fixed » Active

Setting this back to active - this issue seems to persist. There is at least one other isse reporting this problem, see for example http://drupal.org/node/34991 - this issue notes that the problem manifests under PHP5.

chx’s picture

Still an issue?

naudefj’s picture

No. As far as I'm concerned, this issue can be closed.

Tobias Maier’s picture

Status: Active » Fixed

I think its fixed
thanks

Anonymous’s picture

Status: Fixed » Closed (fixed)