JetPack broke the CSS Editor

  • Resolved raccoondog

    (@raccoondog)


    1 year, 7 months ago

    I’d assumed that “Advanced CSS controls” in Additional CSS was part of the W-P distro or the theme. Actually, it turned out to be dependent on JetPack.

    After I enabled this option, the live-preview in CSS Editor no longer worked. (Instead, the frame displayed the site as if there was no Additional CSS.) But disabling JetPack removed the Advanced options and restored the live-preview function.

    JetPack came installed with our multisite, and we don’t necessarily need it. But am posting because the instructions in the Review area say to report problems here.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Alin (a11n)

    (@alinclamba)

    Hi @raccoondog,

    Thank you for reporting this out. I am not familiar with the WordPress theme you mentioned, but it sound like a potential conflict to me. However, if you still want to use Jetpack and avoid this conflict, you can disable the Advanced CSS editor feature from Jetpack. The easiest way to do that is from the All Modules page, following the link: your-site-url/wp-admin/admin.php?page=jetpack_modules&s=custom%20css

    Let me know if this helps.

    Plugin Support Jay

    (@bluejay77)

    Hi there,

    It has been more than one week since we have heard from you, so I’m marking this topic as resolved.

    But if you have any further questions or need some more help, you’re welcome to reply here or open another thread.

    Thread Starter raccoondog

    (@raccoondog)

    Hi @alinclamba,

    Thanks for pointing out the module configuration page for JetPack, and sorry for the delay getting back to you

    Fortunately, we probably don’t need JetPack – which means we are mostly reporting rather than requesting support.

    But to add some more details…

    When I enabled the JetPack Custom CSS module on an unrelated website (and not a multi-site), my reported issue doesn’t exist there.

    And unfortunately, I can’t access the JetPack modules page using the URL heirarchy you provided on the multisite with the issue – otherwise I would have tried disabling the Custom CSS module, if only to confirm your suggested fix.

    • This reply was modified 1 year, 7 months ago by raccoondog.
    Plugin Support Alin (a11n)

    (@alinclamba)

    Hi @raccoondog,

    Thank you for sharing the additional details, and please don’t worry about the delay in our response.

    It’s a good idea to disable the module from Jetpack settings, and if you decide to use Jetpack again, please let us know. We’ll be happy to help you again.

    We will mark this thread as solved for now, but if you have any further questions, please don’t hesitate to reach out to us.

    Best regards.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘JetPack broke the CSS Editor’ is closed to new replies.