Double menu when using Ubermenu?

Hi Brent,

Can you first try disabling it in Customizer > Layout > Primary Navigation > Navigation Location?

Let me know if this works.

Just tried it, and it removes both menus. So no luck unfortunately :-(

I know Ubermenu can work with GP as I've seen it recommended, so I'm sure it is a conflict somewhere. But just can't figure it out since I haven't had this problem previously.

For the record, previous theme was Avada, which they have had on their site for many years. So I'm excited to get them off of it :-)

Brent

Thought that might happen...Can you try this CSS:

.main-navigation .menu-toggle {
    display: none !important;
}

Adding CSS: https://docs.generatepress.com/article/adding-css/

Let me know.

That seems to remove one of them on mobile sizes, but not on desktop resolutions. When using that CSS, it keeps the menu toggle that is shown on top in my image above, and removes the other menu. But again, only on mobile. I'm sure I could set up an !important rule or something using media queries, but would love to figure out if this problem is an actual conflict or not?

Thanks.

Brent

Can you try the code above again? I edited after posting it initially.

Can't tell without seeing the site but some other user had similar problem before I believe: https://generatepress.com/forums/topic/uber-menu-issue/

Let me know.

Ok, so an update. I tried the newer code above, but it didn't work. I went to the thread you referenced and used the following code:

@media (min-width: 960px) {
.ubermenu-responsive-toggle-main.ubermenu-responsive-toggle-align-full {
display: none;
}
}

It DID work......kind of. It makes everything work, but when the viewport is reduced below 768px, a second mobile menu still appears.

To make things easier, I have uploaded everything to a test site of mine that is live, and set everything to the state that I have them on the local site. You can see it here:

http://www.conservetruth.com

When you resize down below 768px, you will see the menu appear. It's the one that is controlled by the Customizer>Layout>Primary Navigation. You can see I gave it a custom name, lol.

The kicker is that the menu in question that appears doesn't even work. It doesn't actually display any menu items when clicked. The other menu, which is supplied by Ubermenu, does.

Now, I know I can probably use another media query to hide that one. But I'm just thinking there might be another way. So look at the site above and see what you find, and if you need a login, I can send a Privnote to you or a private message or whatever you prefer.

Going to bed soon, so if I don't reply right away, that's why. But will try to stick around for a bit. Thanks!

Brent

This should do it:

@media (max-width: 768px) {
    .main-navigation .menu-toggle {
        display: none;
    }
}

That code works :-) I kind of figured that would be the solution, but didn't know if it was intended behavior or something that is worth addressing. I'm ok with the CSS answer (and using Simple CSS, which rocks!). So I appreciate the help!

Brent

Glad we could help :)

So just a quick question on this, if you can answer. Would it be cleaner to do the method above, with the menu in GP "turned on", but being selectively hidden, or would it be cleaner to turn it off in the Customizer, and then insert the Ubermenu directly using GP Hooks? Any downside to that compared to the method discussed in this thread? Thanks.

Brent

Hi Brent,

I would say it would be cleaner if you can get it to work with GP Hooks.
Then GP menu wouldn't be loaded then hidden by CSS. The speed maybe slightly faster :)

Let me know if this answers your question.

Thanks. That was kind of my thinking. I just didn't know how much code was loaded (or turned off) based on having the GP menu load or not. I'll do a test and see which is faster, but just wanted to be sure I wasn't missing something. Thanks!

Brent

Sounds good. Let us know the result.
I'm interested to know if there would be noticeable difference as well :)

Most likely wouldn't be able to tell the difference speed-wise, but worth a shot :)