My main menu is a taxonomy menu. I gave all the items a weight, so the menu, submenu and their children are shown in the right order in my menu. That works fine in the standard Drupal menu. But however in TB Mega Menu the aren't in the right order.

The menu-items are in the right order but the submenu-items aren't. They are mixed up. I tried to change weights, but that doesn't help. I tried to swap places but that doesn't seem possible. How the get them in the order I want ?

Comments

sagesolutions’s picture

StatusFileSize
new63.96 KB
new184.71 KB

I'm having the same issue but I am not using a taxonomy menu. I am using a regular menu, and the submenu items do not get displayed in the correct order. It seems like every time I save the TB Mega Menu, the order changes in the display.

Basically, I need the menu sub-items to display in the same order as the admin/structure/menu/manage/main-menu page

ogursoy’s picture

I have same probem

lluisandreu’s picture

Same problem here when using Taxonomy Menu and using "Reset to alphabetical"

eda1’s picture

Same basic problem: two sub-columns are not displayed in the order created in drupal's menu structure and need to change places. I tried adding/removing/breaking the columns and I've also tried changing the weights, but nothing helps.

jacquelynfisher’s picture

We were experiencing this same issue.

In Structure > Menu > Main Menu we had ordered our links:

Top-level Link:
- Link 1
- Link 2
- Link 3
- Link 4

However, the TB Mega Menu were displaying the sub-links in a strange order:

Top-level Link:
Link 1 | Link 3 | Link 4 | Link 2

How we were able to resolve this problem on our site was to re-install a fresh, clean copy of TB Mega Menu, run update.php, and clear cache.

kienan91’s picture

i had error same https://www.drupal.org/node/2570607 ! how to fixed it ! thanks !

bmx269’s picture

This issue has appeared on one of the submenu's not all.

bmx269’s picture

Going into the drupal menu list links, reorder one item, then save, then put it back where you want it, and then save again, fixed the issue for the specific out of order menu.

SravanthiAll’s picture

I had the same issue. I went back to the Menu items and re arranged them back to the same order and saved. I had to do it for each sub menu item. It worked well. It also fixed another issue with Grid settings of multiple columns.

SravanthiAll’s picture

Thank you bmx269, I did the same reorganizing of menu items for each sub menu level and it worked well. It also addressed the issue of setting multiple columns width.

kienan91’s picture

hi @bmx269 ! I tried do your told but this error still !

mrconnerton’s picture

#8 solved it for us as well, but there is obviously still a but. The normal menu system uses the mlid I assume to weight when there isn't a real weight.

implemagician’s picture

StatusFileSize
new44.71 KB
new43.17 KB

I've run into this before particularly with sub-menus that are broken out into columns.

In my before image, the order of the links were sibley, halverson, hawthorne, and lakeview when I first set them to break to a new column. When I re-ordered them in the normal Drupal menu admin screen (list links) to be halverson, hawthorne, lakeview and sibley, the columns are still in the old order. I went back to the config tb_mega_menu screen and removed the breaks so that the drop down was normal (1 column) and saved and refreshed. The links were now in the correct order and I was able to break the columns again so it looks like the after picture.

TL;DR If you re-order your links after you've made columns in the tb_mega_menu admin, they won't update in the mega menu.

deepikakaran’s picture

Thanks! #13 worked for me. Its a good workaround.

Joel_XN’s picture

Thanks! #13 That's work in my case with TB Megamenu 7.x-1.0-rc2

rbrownell’s picture

Status: Active » Closed (outdated)

Thanks for the report and for contributing to the TB Mega Menu issue queue.

Drupal 7 reached end of life on January 5, 2025 and is no longer supported going forward.

As part of wrapping up Drupal 7 support for this project, issues that do not include a code-based resolution (including issues where the only patch is out of date and requires a re-roll) are being closed as Outdated as part of this cleanup.

This closure reflects the end-of-life status of Drupal 7 and the absence of an up-to-date fix we can act on, not the validity of the issue itself.

If the issue applies to a currently supported version of Drupal, please open a new issue with updated details.

Thanks again to everyone who contributed during Drupal 7’s lifecycle.

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.