Possible Bug Report

  • Resolved drokkon

    (@drokkon)


    11 years, 5 months ago

    It’s pretty well known that RocketTheme’s Gantry plugin doesn’t play nice with JetPack, and I know it’s not your fault. That darn spin.js error breaks things like the widget page, where you can’t drop down the widget areas, for example.

    Anyway, on my multisite installation, I find myself disabling JetPack from the network level regularly for a few minutes to mess around with widgets, for example, and then reactivating it. Lately, however, I’ve noticed some strange behavior: once reactivated, JetPack is automatically “connected” for all two dozen blogs on my network EXCEPT for the primary blog. Each time, I have to go into that primary blog and manually reconnect JetPack to WordPress. I have no idea why, and perhaps this isn’t your problem since I shouldn’t be constantly activating and deactivating it anyway, but I thought I’d let you all know.

    Thanks for a great plugin! Would still love to see IntenseDebate make an appearance. ??

    https://www.ads-software.com/extend/plugins/jetpack/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    That darn spin.js error breaks things like the widget page, where you can’t drop down the widget areas, for example.

    We know about this issue. It’s caused by a namespace conflict between Mootools’ Spinner function, and Jetpack’s own spinner. Although not that many people use Mootools in WordPress themes, RocketTheme does, and we would need to find a solution to solve this conflict.

    Once reactivated, JetPack is automatically “connected” for all two dozen blogs on my network EXCEPT for the primary blog. Each time, I have to go into that primary blog and manually reconnect JetPack to WordPress.

    Instead of deactivating the Jetpack plugin, you could try to activate a small plugin that would disable Jetpack’s spinner function while you make your widget changes. You can use this plugin:

    https://i.wpne.ws/PRX9

    The code is available here:
    https://gist.github.com/jeherve/5714915

    You could also try to deactivate all Jetpack modules that do require the spinner:
    Carousel, Custom CSS, Infinite Scroll, Notifications.

    I hope this helps.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    My colleague George proposed a better plugin, that you can download from here:
    https://github.com/georgestephanis/nuke-spin
    https://github.com/georgestephanis/nuke-spin/archive/master.zip

    Thread Starter drokkon

    (@drokkon)

    Great idea! Thank you. I wasn’t really expecting a solution, but I thought it would be nice just to point out the reactivation “bug,” if it is, indeed, a bug.

    Thread Starter drokkon

    (@drokkon)

    BTW – That worked like a charm! I’ll make sure that the folks over at the RocketTheme forums hear about this. Thanks!

    Why not rename the Spin class in the JetPack to resolve the issue? From what I understand, the Spin class is in MooTools core so no way to modify that, but the one in the plugin would be easily modifiable, no?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    @shazdeh That’s one of the solutions we’re considering, indeed. We’ll work on getting this fixed in a next jetpack release.

    You can follow along here if you like:
    https://plugins.trac.www.ads-software.com/ticket/1768

    Brilliant; thank you! ??

    Thread Starter drokkon

    (@drokkon)

    Did 2.3 address this issue? I saw something about spin.js in the changelog, but it was over my head.

    Plugin Contributor George Stephanis

    (@georgestephanis)

    We updated spin.js to use the latest canonical version, but as it’s a third-party library that we use, modifying the function names could break compatability with any other extensions or themes that use the common javascript files.

    Here’s the script’s github page, if you’d like to browse their code, and request something upstream: https://fgnass.github.io/spin.js/

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Possible Bug Report’ is closed to new replies.