Problem/Motivation

I want own blocks in mega menu. Using 3x version of modul and Drupal 11 (before hooks update).
It is not possible to add Block to column as reported in manual (for version 2x, i know) here:
https://www.drupal.org/docs/contributed-modules/the-better-mega-menu/how...

I can see my blocks in dropdown in GUI but after selecting given block and apply SAVE button, selection disapered.

There are more bugs, like same CSS class to every created column, but I need specific classes.
In this state input for CSS class next to block selection is useless. I need specific class for each column item.

At this state is wasting of time using 3x
Not sure how good is 2x with Drupal 11

Proposed resolution

Fix it.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

    Comments

    marianrk created an issue. See original summary.

    ravi kant’s picture

    Hi marianrk,

    Are you getting the error in the browser console or in Drupal's 'Recent log messages'?
    Attach the screenshot if you are getting error.

    bron.f’s picture

    I am having this problem too. At first I was getting a chosen JavaScript error but that was fixed with this patch tb_megamenu-jquery4-fix-3530244-1.patch. The blocks come up in the dropdown now but if I add them I can't see the block content and when I click save it says 'config saved' but the block is not added to the menu.

    If I check the logs it seems like it can't find the custom blocks. The Message is:

    The "block_content:c1fbe166-c475-4705-9af8-14859fa0c7e8" block plugin was not found

    . I have created a new custom block and have added to the structure > block layout. There are no JavaScript errors in the console anymore.

    rbrownell’s picture

    Assigned: Unassigned » rbrownell
    bron.f’s picture

    rbrownell’s picture

    Status: Active » Closed (cannot reproduce)

    @marianrk

    Thanks for posting this issue, I'm not able to reproduce this issue on a fresh checkout (and build) of 3.0.0-alpha5 on Drupal 11.

    There have been reports that this issue can be resolved by following the guidance on https://www.drupal.org/node/3471262 including patching TB Mega Menu. The patches on the other issue have already been merged to the 3.x dev branch and will be included in the next release.

    Regarding wanting to add custom classes to individual columns this functionality already exists but the UI does not clear the field between context switches (i.e. selecting one column, typing in a value, and then switching to another column to make changes). This issue should be filed as a separate bug report.

    In the interests of issue clarity, I am going to close this ticket. If the custom column classes UI bug still matters to you, I would encourage you to file a new issue specific to this problem with a detailed description, screen shots and any relevant console logs.

    Now that this issue is closed, review the contribution record.

    As a contributor, attribute any organization that helped you, or if you volunteered your own time.

    Maintainers, credit people who helped resolve this issue.

    rbrownell’s picture

    rbrownell’s picture

    One point of advice for users who are landing on this page for help. In order to add a block you must first add a column. Trying to add a block to a column that was automatically produced because of menu items does not always work.