Closed (fixed)
Project:
Drupal core
Version:
x.y.z
Component:
block.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Aug 2005 at 15:05 UTC
Updated:
8 Feb 2006 at 19:00 UTC
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:
has anyone seen the same?
solutions? ideas?
I want also point you also to this error: error on /user/*/edit
Comments
Comment #1
naudefj commentedI had the same problem and had to restore back to 4.6.0. Hope it will be fixed soon...
Comment #2
Uwe Hermann commentedYep, I can reproduce this in HEAD. Will take a closer look if I get around to it.
Comment #3
Tobias Maier commentedthe main issue was fixed in http://drupal.org/node/29506
but there are still the many table rows...
has anyone else seen this?
Comment #4
jakeg commentedI'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?
Comment #5
Tobias Maier commentedtoday 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
Comment #6
killes@www.drop.org commentedIs this still an issue?
Comment #7
Tobias Maier commentedi dont think so...
Comment #8
puregin commentedSetting 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.
Comment #9
chx commentedStill an issue?
Comment #10
naudefj commentedNo. As far as I'm concerned, this issue can be closed.
Comment #11
Tobias Maier commentedI think its fixed
thanks
Comment #12
(not verified) commented