Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This is a pretty stupid issue, and I'm wondering how it is nobody else has caught it so far.
Steps to reproduce:
1.) Put DHTML on all your menu blocks.
2.) Create a custom block. Make sure that the custom block has the same delta value as that of a menu block (ie, they're identified by block:{n} and menu:{n})
Expected result:
The custom block is displayed normally.
Actual result:
The content is stripped from the custom block.
Diagnosis:
DHTML Menu needs to identify blocks by module as well as delta. I have a patch here that fixes this, including an update hook.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | dhtml_menu-block-delta-276507-1.patch | 4.72 KB | cburschka |
Comments
Comment #1
cburschkaHere we go. There's a bit of a concept issue involved here. The module index is missing because the settings are stored per menu name rather than per block:delta. This breaks because what is being replaced is a block, not a menu.
Perhaps a future version can interface with the Menu API rather than the Block API, but for now we have to use block:delta instead of the menu name to index these settings.
Comment #2
cburschkaCommitted.
This is the first bug to be fixed since the last release. (Just keeping track.)
Comment #3
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.