After saving the change of a megamenu-style i.e. from dark to blue is not displayed on the user-site.
Logged in as an admin the style has changed working correct: the color is blue and the animation is elastic.
But logged out as a normal user I see the color is black instead blue and animation is elastic instead slide.

I cleared the cache many times.
Query is 1.7
I'm using a cdn-subtheme, 3.5 drupal bootstrap-theme and TB Mega Menu last 7.x-1.x-dev-version.

Comments

quixxel created an issue. See original summary.

quixxel’s picture

quixxel commented

It seems that this issue/bug is belonging to (non existing?) multilingual settings of TB-MegaMenu.

Looking into the db I found a quick and dirty solution for me:
The column block_config shows two rows: one for every language:

First row (language for admin and authenticated user) was
{"animation":"fading","duration":400,"delay":200,"style":"blue","auto-arrow":"1","always-show-submenu":"1"}
and the second for normal user was
{"animation":"elastic","duration":400,"delay":200,"style":"black","auto-arrow":"1","always-show-submenu":"1"}

The solution for me to solve my problem was to copy the value of the first row into the second and it works.

Where else could I adjust the settings for different languages?

quondam’s picture

quondam commented
Assigned: Unassigned » quondam
Status: Active » Needs work
quondam’s picture

quondam commented
Assigned: quondam » Unassigned
Status: Needs work » Closed (works as designed)

As noted in #2 this issue pertains to multilingual sites. The configuration for a given megamenu is saved to a language-specific row in the database, capturing the current language at the time the configuration is changed. For example in the case of URL-based language switching on a site with English set as the default language and Spanish as a selectable translation:

  • /admin/structure/tb-megamenu allows for configuration of the English menu
  • /es/admin/structure/tb-megamenu allows for configuration of the Spanish menu

Since the configuration for each translation is stored separately, changing the style or animation for the English menu will not sync those changes to the Spanish menu - and vice-versa. This is by design to allow for customizations across languages (e.g. language-specific additional classes); in order to accommodate that level of customization each language is required to have its own instance of the configuration object.

Ultimately this is an issue of documentation (or more specifically lack thereof) - a topic already more broadly on the radar of the current module maintainers. Anyone encountering this issue who's looking to keep config identical across languages will need to manually set configuration to match one another by using their site's language switching mechanism to access language-specific TB megamenu routes like those listed above.

Ideally there would be a language switching mechanism available as tabs or local tasks on the TB Megamenu configuration pages. I've created a new feature request to track that.