Jetpack update breaks WordPress 3.5

Alan Buckingham
Jan 7, 2013

Jetpack, the popular stats plugin for WordPress, has released several updates recently. The latest, which came yesterday, January 6th, brought an unwelcome gift for those who have upgraded to the recent WordPress 3.5 platform. The latest version of Jetpack, 2.1.1, disables some key functionality within WordPress -- namely the ability to add media.

Users who upgraded were surprised when attempting to edit a new post. When clicking the "Add Media" button, which WordPress added in version 3.5, nothing happens. Nothing at all. No error message, no continuous running. Just nothing.

While it took a little while, as the day went on the WordPress support forums began lighting up with customers demanding to know what had happened to their beloved content management system. This is not the first WordPress 3.5 problem either. Previously another plugin, Bulletproof Security, caused some issues upon upgrade. In fact, that one was even tougher to fix, involving FTPing into a site to remove HTaccess from the WP installation.

The problem caused by Jetpack will prove somewhat easier to fix. Initially I attempted to disable the plugin, as it was the only update that occurred before the problem reared its head. That did not solve the issue.

However today, one clever user on the WordPress forums -- paulbienkowski -- found that you not only need to disable Jetpack, but also do a reinstall of WordPress 3.5 in order to solve this problem. Meanwhile, another user also reports that, in addition to "Add Media", the update also broke the linking. Still another poster said that enabling Jetpack, but not connecting it to, would get everything working again.

So far there has been no mention of any of this on the Jetpack web site, at least as far as I could find. However, the developers are usually on top of these things, so I would expect a fix to be coming within the next day or two. For now, all you can do is follow what I have outlined above.


Previous Post: «
Next Post: «


  1. Christopher Finke said on January 9, 2013 at 12:18 am

    Every report of breakage in 3.5 so far has been traced back to another plugin doing something it shouldn’t, like manually loading old versions of jQuery libaries.

    In the paulbienkowski thread alone, three different plugins (CevherLike Facebook Like Popup Plugin, Simple Slideshow, and Find Me Elsewhere) were found to be responsible for the breakage, not Jetpack.

    If you have any reports WordPress 3.5 breaking with only Jetpack installed, please do report it in the support forum: Until then, you may want to update your post title.

  2. Carl said on January 8, 2013 at 8:02 am

    Thanks for the heads up mate!

  3. RG said on January 8, 2013 at 5:51 am

    @Pablo, Martin has done that before, for example

  4. Pablo said on January 8, 2013 at 5:37 am

    Martin, I think it’d be interesting if you wrote an article (or two) enumerating the WordPress plugins you’re currently using on Ghacks, and a short description of each one.

  5. Chetan said on January 8, 2013 at 1:50 am

    I was just about to update but saw your post. Now I am waiting for more response before updating my plugin. Should I update or wait?

  6. Anne said on January 7, 2013 at 10:26 pm

    I updated mine, and got a 500 internal error. Removing jetpack restores my site. I like using jetpack. Oh well will have to wait for further updates and see if it fixes it. Thanks for this article.

  7. Mosh said on January 7, 2013 at 9:59 pm

    Mine’s working fine (touch wood). Three blogs all on 3.5 with JetPack 2.1.1, so I guess there must be something else involved.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.