Hello,

Something strange happens when I activate the DHTML module. All my menus disappear. It does not matter what team is used.

I tried to find the answer into the permission table, but could not find anything.

Any hints?

Thanks.

Comments

cburschka’s picture

cburschka
they
commented
Status: Active » Postponed (maintainer needs more info)

Hello, do you have Theme Developer enabled, by chance? There appears to be a bug in it that causes these blocks to disappear.

Otherwise, it would be good if you could post the following:

- attach the HTML source of the front page as a text file, so I can see if it is the entire block, or just the content, or something else.
- list any contributed modules you have enabled.

yoeld’s picture

yoeld commented

Yes, I am using the Devel module.

Indeed, disabling the Devel module solves the problem.

Any idea when this will be solved?

Thanks for your support.

cburschka’s picture

cburschka
they
commented
Status: Postponed (maintainer needs more info) » Postponed

Sorry, not a clue.

This is caused by a recent change in Devel, and affects other modules besides this one. If the makers of Devel find something I need to change in my module, I'm perfectly willing to do that, but I can't do the detective work. ;)

cburschka’s picture

cburschka
they
commented
Title: Activating DHTML make all menus disappear » DHTML Menu conflicts with Theme Developer (blocks disappear)
Category: support » bug
rj’s picture

rj commented

Hey I was having this problem too, I uninstalled and reinstalled DHTML and now it works fine. Unfortunately I can't get the problem to repeat.........

roald’s picture

roald commented
Version: 6.x-3.3 » 6.x-3.4

I'm having the same issue, and am not able to resolve by uninstalling / reinstalling.
* drupal 6.11
* devel 6.x-1.16
* DHTML Menu 6.x-3.4

All menu blocks disappear, other blocks remain.

Disabling either Devel Theme Developer or DHTML Menu makes the menus appear again

cburschka’s picture

cburschka
they
commented
Version: 6.x-3.4 » 6.x-3.x-dev

3.x-dev is the place where this will be fixed.

zapscribbles’s picture

zapscribbles commented

Subscribe

zapscribbles’s picture

zapscribbles commented

Looks like this is fixed in 3.5 - thanks guys!!!

zapscribbles’s picture

zapscribbles commented

Apologies - I spoke to soon. But keep up the good work :-)

cburschka’s picture

cburschka
they
commented
Status: Postponed » Closed (won't fix)

Yeah, I've tried to tackle this a few times and eventually gave up in disgust. The learning point here is that you can't use what amounts to extreme debug mode and still expect other modules to work normally both with the altered theme layer and the altered DOM.