- Issue created by @dco
- 🇺🇸United States themodularlab
@dco,
When adding a block to TBMM, the block has to be loaded in a block region via the block admin ui for Drupal and thus the MM to be aware of it. Our recommendation is to use a hidden theme region. It will also require a cache clear for TBMM to be aware of new blocks.
- 🇫🇷France dco
Hello
It works, the blocks are listed now. Thank you for your quick reply.
But when trying to add a block in a columns it just show a message showing the json ajax reponse and nothing appears in the column.
I don't have much time but I'll try to investigate and keep you informed.On Drupal 11.0.1
Best regards,
David
- 🇮🇳India gokul.jayan
gokul.jayan → made their first commit to this issue’s fork.
- 🇮🇳India gokul.jayan
Hi, the issue was caused by a deprecated jQuery function. I’ve resolved it and created a merge request. Please review it.
- 🇮🇳India gokul.jayan
gokul.jayan → changed the visibility of the branch cherry-pick-9c439cfc to hidden.
- 🇮🇳India gokul.jayan
gokul.jayan → changed the visibility of the branch cherry-pick-9c439cfc to active.
- 🇮🇳India gokul.jayan
gokul.jayan → changed the visibility of the branch cherry-pick-9c439cfc to hidden.
- 🇬🇧United Kingdom nijolawrence
nijolawrence → changed the visibility of the branch cherry-pick-9c439cfc to active.
- 🇬🇧United Kingdom nijolawrence
nijolawrence → changed the visibility of the branch cherry-pick-9c439cfc to hidden.
- 🇬🇧United Kingdom nijolawrence
We were able to use the functionality of adding blocks in one of our Drupal 11 projects with the above patch applied.
- 🇭🇷Croatia devad
The ugly
{"content":" \u003Cdiv class=\u0022tbm-block\u0022 data-type... ... ...error has disappeared after I applied the merge request patch and I was able to add Drupal view block as a submenu and save it successfully. So, I suppose this fix is ok for this issue. Therefore marking it as RTBC.My config: Drupal11 + latest TBMM .dev
----
But...
Although the block is visible inside the Megamenu configuration page - my new submenu is not visible at the frontend. No new errors are available both inside drupal log or inside browser's JS console. Hard to debug. I'll make new issue for that or join some already created issue for that.