WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Multisite, Jetpack, and Networkwide Menu (10 posts)

  1. novacode7
    Member
    Posted 2 years ago #

    I'm using multisite to manage a K-8 school's website. I'm using an awesome networkwide menu plugin that allows my main menu to appear on each site.

    I noticed that the Jetpack plugin is interfering with this lightweight menu plugin. When Jetpack is active on one of the sub-sites the menu doesn't load properly and won't drop down when viewed in IE, Firefox, and Safari (but it oddly works perfectly in Chrome). Any ideas?

  2. It's probably due to your CSS. Without being able to see your site, I would GUESS that you're defining your menu with the same classes and IDs as Jetpack.

    I'd rename them to sitename-classname (like ipstenu-menu and so on) to ensure you don't conflict.

  3. novacode7
    Member
    Posted 2 years ago #

    Thanks for your reply, Ipstenu. Here's the website in development.

    I tried renaming the subsite's menus but to no avail. For the time being I've simply disabled Jetpack on the subsites (though it works fine on the main site).

  4. Which menu is it breaking? The black one at the top or the one below the logo?

  5. novacode7
    Member
    Posted 2 years ago #

    The one below the logo. I just reactivated Jetpack on the 1st Grade subsite for testing. Only after reconnecting Jetpack to my WordPress.com account did the conflict occur again. It affects both the menu and the posts, which no longer appear either. Thanks for looking at this!

  6. With Jetpack activated, try turning OFF the modules you aren't using (or really all of them). See which one is breaking it.

  7. joshhuntnm
    Member
    Posted 2 years ago #

    I seem to have a similar problem. The top line of the menu worked, but the sub-menus went away. it also seemed to cause some problems with the front page. The theme is Ezekiel.

  8. novacode7
    Member
    Posted 2 years ago #

    After a recent Jetpack update my problem was resolved without me even having to try deactivating the modules (so I'm not certain what caused the conflict).

  9. We're gonna call it a Jetpack CSS snafu ;)

  10. novacode7
    Member
    Posted 2 years ago #

    Thanks, Ipstenu - that about sums it up!

    Your moderation on WordPress.org is invaluable!

Topic Closed

This topic has been closed to new replies.

About this Topic