Title: JetPack is deregistering javascripts
Last modified: August 20, 2016

---

# JetPack is deregistering javascripts

 *  [Steph Wells](https://wordpress.org/support/users/sswells/)
 * (@sswells)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/)
 * I’m a plugin developer, and JetPack is causing big issues for our users. It’s
   been over a month, and no fix has been released. Formidable uses the wp_register_script
   hook, but by the time it gets to the footer hook, the scripts are no longer registered.
   Why is JetPack deregistering javascripts from other plugins?
 * I would expect a plugin written by WordPress to not cause so many plugin conflicts
   with plugins that are doing things the right way, and if there are numerous conflicts,
   to get an update out in a timely manner.
 * [http://wordpress.org/extend/plugins/jetpack/](http://wordpress.org/extend/plugins/jetpack/)

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

 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416007)
 * Could you give me more details about this issue? I haven’t received any reports
   of conflicts between Formidable Forms and Jetpack until today, but I’d be happy
   to investigate further and see if we can solve any conflicts you may have find
   between Jetpck and one of the plugins you use on your site.
 * Jetpack doesn’t deregister any libraries from other plugins. I installed [Formidable Forms](http://wordpress.org/extend/plugins/formidable/)
   on a test blog, and `formidable.js`was correctly included in the footer.
 * If you experience issues on your own site, could you post the URL, so I can have
   a look?
 * Thanks!
 *  Thread Starter [Steph Wells](https://wordpress.org/support/users/sswells/)
 * (@sswells)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416037)
 * Thanks for the reply. I don’t personally have JetPack installed anywhere, but
   here are a few reports on our help desk with details (there are other private
   ones as well):
    [http://formidablepro.com/help-desk/display-graph/](http://formidablepro.com/help-desk/display-graph/)
   [http://formidablepro.com/help-desk/layout-of-forms-gone-awry/](http://formidablepro.com/help-desk/layout-of-forms-gone-awry/)
   [http://formidablepro.com/help-desk/signature-addon-field-stopped-working-with-update/](http://formidablepro.com/help-desk/signature-addon-field-stopped-working-with-update/)
 * This thread says it’s resolved, but it’s not:
    [http://wordpress.org/support/topic/jetpack-contact-forms-are-broken-after-204-update](http://wordpress.org/support/topic/jetpack-contact-forms-are-broken-after-204-update)
 * The pro version is probably needed to see the deregistering. I’ve added an account
   so you can install the full version. Let me know what I can do to help. I was
   going to debug it myself, but since JetPack doesn’t work locally that didn’t 
   work out so well.
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416039)
 * Thank you for all the examples!
 * > [http://formidablepro.com/help-desk/layout-of-forms-gone-awry/](http://formidablepro.com/help-desk/layout-of-forms-gone-awry/)
   > 
   > [http://formidablepro.com/help-desk/signature-addon-field-stopped-working-with-update/](http://formidablepro.com/help-desk/signature-addon-field-stopped-working-with-update/)
 * Unfortunately, all sites seem to have disabled Jetpack, so I can’t reproduce 
   the issue on their site.
 * > [http://formidablepro.com/help-desk/display-graph/](http://formidablepro.com/help-desk/display-graph/)
 * This issue seems to be a bit different from the others, since the issue was related
   to the output of the shortcode. We might have fixed this issue in [r660826](http://plugins.trac.wordpress.org/changeset/660826).
   This fix will be included in the next Jetpack release, but the user can already
   download and install the Beta version of our next release here:
    [http://wordpress.org/extend/plugins/jetpack/developers/](http://wordpress.org/extend/plugins/jetpack/developers/)
 * > This thread says it’s resolved, but it’s not:
   >  [http://wordpress.org/support/topic/jetpack-contact-forms-are-broken-after-204-update](http://wordpress.org/support/topic/jetpack-contact-forms-are-broken-after-204-update)
 * This thread was related to a different issue. It was fixed in [r647091](http://plugins.trac.wordpress.org/changeset/647091)
   and the fix was released with Jetpack 2.1 a few weeks ago.
 * > The pro version is probably needed to see the deregistering. I’ve added an 
   > account so you can install the full version. Let me know what I can do to help.
 * Thank you. I used that Pro account to create different forms, based on the existing
   templates. I inserted these forms on different Pages, and on Pages where I also
   inserted Jetpack Contact forms, but I didn’t experience any issues. `formidablepro.
   css` and `formidable.js` were correctly loaded on the Pages.
 * Could you ask the users to download the latest Jetpack Beta, and see if they 
   can still reproduce the issue?
    [http://wordpress.org/extend/plugins/jetpack/developers/](http://wordpress.org/extend/plugins/jetpack/developers/)
 * if that doesn’t help, I should be able to investigate further if I can see the
   issue on their site. Do not hesitate to ask them to post here, I’ll be happy 
   to help!
 *  [markslang](https://wordpress.org/support/users/markslang/)
 * (@markslang)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416040)
 * Jeremy,
    I am one of the Formidable Pro users having the problem with Jetpack.
   My site busacad.org under Pre-enrollment has a Formidable Pro form. I have Jetpack
   2.1.1. I just enabled Jetpack, and it breaks the signature part of the form at
   the bottom. I deactivated, and everything is back working again. I had reported
   this under the thread [http://wordpress.org/support/topic/jetpack-contact-forms-are-broken-after-204-update](http://wordpress.org/support/topic/jetpack-contact-forms-are-broken-after-204-update)
   which is now listed as resolved. Perhaps that was a bad place because that thread
   referred to the Jetpack forms. However, Jetpack has caused me problems since,
   I believe, 2.0.4. (It did not cause any problems when I first created my form
   on the site around October 2012.) All subsequent releases still had the issue,
   and the message board had lots of other people complaining about Jetpack destroying
   their layouts. I am not sophisticated enough to understand what the problem is,
   I just know that Jetpack breaks Formidable Pro.
 *  I have Jetpack disabled now because this site is actively recruiting people 
   with that form. I can try to activate for a given period of time if that will
   help. Just suggest some windows of time that will work for you.
 * Mark Lang
 *  Thread Starter [Steph Wells](https://wordpress.org/support/users/sswells/)
 * (@sswells)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416041)
 * [@jeremy](https://wordpress.org/support/users/jeremy/), maybe you could try adding
   a time field to your form and see if jquery.timePicker.js is loaded in the footer?
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416044)
 * [@mark](https://wordpress.org/support/users/mark/) Now would be a good time, 
   if that’s ok with you.
 * However, we’ve released 2 updates of the jetpack plugin since 2.0.4, so you will
   want to update to the latest version before to activate it.
    Even better, it’d
   be great if you could install our latest Beta version, available here: [http://downloads.wordpress.org/plugin/jetpack.2.1.2b4.zip](http://downloads.wordpress.org/plugin/jetpack.2.1.2b4.zip)
 * Once you have installed this new version, could you please post a link to the
   problematic page if you still experience issues?
 * Thank you!
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416045)
 * > maybe you could try adding a time field to your form and see if jquery.timePicker.
   > js is loaded in the footer?
 * I just tried it, and `jquery.timePicker.min.js?ver=0.3` is indeed loaded in the
   footer. Are there any other fields you’d like me to try?
 *  Thread Starter [Steph Wells](https://wordpress.org/support/users/sswells/)
 * (@sswells)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416048)
 * You could try installing the signature add-on and adding a signature field to
   your form? This is the problem markslang is having. If it works for you, I think
   that would verify that the issue has been resolved.
    [http://formidablepro.com/knowledgebase/formidable-signature/](http://formidablepro.com/knowledgebase/formidable-signature/)
 *  [markslang](https://wordpress.org/support/users/markslang/)
 * (@markslang)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416054)
 * Jeremy,
    I updated Jetpack to the 2.1.2b4 version you supplied above by ftp overwriting
   the folder and activating. The Formidable Pro form is still broken. The signature
   at the bottom is not displaying correctly, and the graphical signature feature
   does not work at all. I will leave this version of Jetpack activated on the site(
   busacad.org) until sometime this evening to give you a chance to review. when
   you get what you need to see, please respond so I can deactivate and get the 
   form working properly again.
 * Mark
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416055)
 * [@mark](https://wordpress.org/support/users/mark/) Thank you! Could you try to
   deactivate the Sharing and Publicize modules in Jetpack, and let me know if this
   helps?
 * You can find out how to disable Jetpack modules here:
    [http://jetpack.me/support/#turn-off-jetpack-modules](http://jetpack.me/support/#turn-off-jetpack-modules)
 * [@sswells](https://wordpress.org/support/users/sswells/) I managed to reproduce
   the issue with the Signature add-on. I am looking into it now, and will keep 
   you updated.
 *  Thread Starter [Steph Wells](https://wordpress.org/support/users/sswells/)
 * (@sswells)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416056)
 * Thank you! For a little more info, we use wp_register_script to register, and
   then only use the scripts when needed with
    $wp_scripts->do_items( array(‘flashcanvas’,‘
   jquery-signaturepad’) );
 * But do_items isn’t returning anything with JetPack active.
 *  [markslang](https://wordpress.org/support/users/markslang/)
 * (@markslang)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416057)
 * I deactivated Sharing and Publicize as you requested. The form seems to be working
   now. I have left it up on the site busacad.org with those two features deactivated.
 *  Thread Starter [Steph Wells](https://wordpress.org/support/users/sswells/)
 * (@sswells)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416058)
 * I think it’s related to the filter_infinite_scroll_results function in JetPack,
   and something about where we are using do_items (mid page vs footer).
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416059)
 * [@sswells](https://wordpress.org/support/users/sswells/) Thank you.
 * [@markslang](https://wordpress.org/support/users/markslang/) Thank you. As I 
   mentioned above, we’re looking into it at the moment. You can deactivate the 
   whole plugin if you like now.
 *  [markslang](https://wordpress.org/support/users/markslang/)
 * (@markslang)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416062)
 * OK. I deactivated Jetpack just to be safe. I hope you got what you needed.

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

The topic ‘JetPack is deregistering javascripts’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

 * 15 replies
 * 3 participants
 * Last reply from: [markslang](https://wordpress.org/support/users/markslang/)
 * Last activity: [13 years, 6 months ago](https://wordpress.org/support/topic/jetpack-is-deregistering-javascripts/#post-3416062)
 * Status: not resolved