Breaks widgets
-
You won’t be able to drag&drop widgets under the appearance menu while this is activated and connected to WordPress.com
-
I’m sorry to hear you’ve run into issues.
Could you check for Javascript errors in the Widget administration screen? That could help us understand the problem.
You can follow these instructions to open the Javascript Console in your browser:
http://webmasters.stackexchange.com/questions/8525/how-to-open-the-javascript-console-in-different-browsersBasically there is a JQuery error at:
http://www.mydomain.com/wp-content/plugins/jetpack/_inc/jquery.spin.js?ver=3.5.1Uncaught TypeError: Object [object Object] has no method ‘spin’
ignoring: do not inject on explicit file urlsThat error doesn’t appear once I deactivate Jetpack
Thanks for the extra details.
This error could be caused by a conflict between Jetpack and one of your plugins, or your theme.
If your site loads an old version of jQuery, it can create multiple conflicts with WordPress and with other plugins like Jetpack. You can read more about it here:
http://wordpress.org/support/topic/troubleshooting-wordpress-35-master-list?replies=4#post-3547424Could you try switching to a different theme for a few minutes, and check if that solves the issue? If it does, you’ll want to look for the function loading jQuery in your theme’s header.php file, or in the functions.php file. Once you find that function, you can remove it and enqueue the proper version of jQuery as explained here:
http://codex.wordpress.org/Function_Reference/wp_enqueue_scriptIf the issue is not related to your theme, please try to disable all your plugins, one at a time, until the error disappears. You can then edit the plugin to enqueue jQuery using the method I linked to above.
If you do not feel comfortable editing PHP files, you can also contact the theme or plugin author and ask them to solve the issue.
I hope this helps.
Ok I swapped out templates and sure enough that also fixes the problem (although so does swapping out Jetpack).
I brought up the console and it’s still pointing to the jQuery called by Jetpack but it may just be cause that was called second. I can’t find where jQuery is called in my template (not in header.php).
Any way I can find out where that is being invoked?
Can you try searching for mentions of “jquery” in all files? You might want to start searching in functions.php, and in the
inc/
,includes/
,functions/
, or similar folders in your theme.So I grepped the entire theme and there was no jquery calls, which struck me as odd. So went back into the documentation for that theme (RocketTheme) and apparently it uses MooTools in place of jquery. So….it appears as if it’s not a conflicting jquery call?? So why is it complaining about the jquery that Jetpack is using then?
Could you let me know your site URL, or the name of the theme you currently use, so I can have a look at the issue?
Thank you!
I’m using RocketTheme’s Syndicate template
The folks at RocketTheme claim this is a known-issue in the JetPack libraries.
In their words:
There is an error in a JavaScript file from the JetPack library which
causes other scripts on the page to fail, I think it was reported to
JetPack a while back but for now, you can disable the plugin temporary to
make changes in widgets.I think the problem is that the JetPack library adds a JavaScript object
called “Spinner” to the page, which also exists in MooTools library
(http://mootools.net/docs/more/Interface/Spinner) and so it creates a
conflict.Thanks for the extra details. It is indeed a conflict between the 2 spinner functions used in Mootools and in Jetpack. We’ll work on this problem and solve this conflict in the next Jetpack release.
Excellent! Thanks for the update and looking forward to the next release.
Howdy, Kecker!
Unfortunately this isn’t something we can fix directly, as it’s being pulled in via an upstream library (in this case, spin.js)
However, if you’d like to temporarily toggle off Jetpack’s spin.js inclusion, you can install this utility plugin:
https://github.com/georgestephanis/nuke-spin
Activate it to remove the spin functionality from Jetpack, then deactivate it again when you’re done, to let Jetpack’s internal spin operate properly again.
- The topic ‘Breaks widgets’ is closed to new replies.