• Hi, I am noticing that if Jetpack is configured at the mulitisite network level, features like custom css and widget visibility only work for the main site. If Jetpack is simply installed at the network level, but enabled on a site-by-site basis, things seem to work normally (but this defeats the purpose of multisite compatibility somewhat). Is this intended behavior or a glitch? Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thanks for the report. Could you provide me with specific examples of the behavior mentioned above? It would also be helpful if you could provide me with a link to your site, so that I can take a look. Just let me know, and we can go from there. Thanks!

    Thread Starter deviantbono

    (@deviantbono)

    Thanks for your response.

    My main site (Site A) is http://www.indiewebcomics.com and the secondary site (Site B) is http://www.indiewebcomics.com/sulfurandgrease — however, everything I’m describing is on the backend/administrator settings so I’m not sure how much viewing the sites will help.

    The specific behavior is basically:
    1. Network enable jetpack
    2. Log in as admin to Site A
    3. Use the “Appearance -> Custom CSS” menu to customize css like normal
    4. Log in as admin to Site B
    5. There is no “Custom CSS” menu item under “Appearance”
    6. Double check that Jetpack is enabled for Site B
    7. Scratch head

    The other use case is:
    1. Install jetpack but don’t network enable
    2. Go to Site A and enable
    3. Got to Site B and enable
    4. Everything works as normal but defeats the network enable/disable functionality

    @deviantbono: Thanks for the additional information, and sorry for the delay. Could you contact us privately so we can investigate this further? Uou can contact us using the form here:
    http://jetpack.com/contact-support/

    Please make sure to include a link to this thread in your message. Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Limited functionality with multisite (e.g. css & widget visibility)’ is closed to new replies.