Mega Menu for submenu

Posted in: Newspaper
Post count: 31

Hi,

I want to create an mega menu using pages, but it does not work for submenus and the pagebuilder creates a bug.

So, i want to create an an header menu with 3 layers.

Layer 1 – needs to be an tabbed content layout.
Layer 2 – standard menus but it must be inline
Layer 3 – mega menus when i hover standard menus

– Element 1
– – Submenu 1
– – – Mega Menu when i hover Submenu 1
– – Submenu 1.2
– – – Mega Menu when i hover Submenu 1.2
– – Submenu 1.3
– – – Mega Menu when i hover Submenu 1.3
– Element 2
– – Submenu 2
– – – Mega Menu when i hover Submenu 2
– Element 3
– – Submenu 3
– – – Mega Menu when i hover Submenu 3

It is possible to achieve something like this?

Because, i’ve tried creating something like this, but the mega menu does not shows. It only triggers when i am using the Brower DevTools and i cannot understand why. So, i created an WP menu, just like i described earlier, but the Mega Menu only after i open and close the Chrome DevTools.

Also, i’ve tried creating an tabbed content with 3 pages and in each page i have standard WP menus with mega menus. This works just fine, but the page builder stops working when i try to use TagDiv Composer on pages and i get this error: Errors at columns elements: 1(models) : 4(dom). The model does not match the content Current state has involved an issue. You could try an UNDO operation (CTRL+Z / CTRL+SHIFT+Z)

PS: the error does not occur when i edit only the header template.

Can you please help me?

Post count: 35449

HI,

Ok, the mega menu can be made only on the primary level – https://forum.tagdiv.com/mega-menu/ but without the theme you can create:
page menu
mega menu (with and without subcategories)
normal menu
Also, you can use the popup element to create popup menus – https://forum.tagdiv.com/modal-popup/

The “ Errors at columns elements: 1(models) : 4(dom). The model does not match the content Current state has involved an issue. You could try an UNDO operation (CTRL+Z / CTRL+SHIFT+Z)” most of the time the problem is from a shortcode that is not compatible with our theme or a plugin conflict, therefore after you set it with tagDiv Composer and save the page/cloud template, the next time when you try to edit it, you’ll get that error.
If is only for one page or a cloud template (it can be on the header or footer, you can change them for tests and see if the problem persists), this is from some settings/shortcodes set on it and it can be fixed using the page revision https://wordpress.com/support/page-post-revisions/

Thank you!

Viewing 2 posts - 1 through 2 (of 2 total)
The forum ‘Newspaper’ is closed to new topics and replies.