Dear Jetpack community,
I want to apologize, firstly, for pushing multiple updates out to you in one day. We’ve been doing our very best over the last several months to make sure that our releases are stable and tested in as many disparate environments as possible.
In this case, a bug cropped up because of an oversight in how we loaded a compatibility file for bbPress in Jetpack. It wasn’t caught in testing, which is unfortunate. This is a good example, though, of how we learn from our mistakes, improve our processes, and do better with the next release.
For those users effected by this, we decided it would be better to release Jetpack 2.2.4 as soon as possible to resolve this issue.
As always, please get in touch with us if you run into an issue. We’d be very happy to help!
Explore the benefits of Jetpack
Learn how Jetpack can help you protect, speed up, and grow your WordPress site.
Get up to 50% off your first year.
Compare plans
Jetpack 
Thank you for rectifying! 🙂 It’s OK we all learn from our mistakes. You’ve done an amazing job so far. Keep up the great work! 😉
LikeLike
Will there be any threat whilst using the older, pre 2.2.3 version ? Or should we dis-activate jetpack altogether?
LikeLike
There’s no currently known threats for using Jetpack 2.2.2 and there is no need to deactivate the plugin.
LikeLike
Appreciate info, thanks.
LikeLike
* When I load a photo into a post, I’m getting the below message. I can attach the photo anyway, but the below message also shows up on the blog post itself. I’ve never had this happen. What do I do??
Warning*: Missing argument 3 for Jetpack_Custom_CSS::editor_max_image_size() in*
LikeLike
If you are comfortable editing PHP files, you can try this:
Open
/wp-content/plugins/jetpack/modules/custom-css/custom-css.phpand navigate to line 1147.Change
static function editor_max_image_size( $dims, $size, $context ) {tostatic function editor_max_image_size( $dims, $size, $context='' ) {.We have a fix for this in our development branch.
LikeLike
I like Jetpack but wonder are you going to do something about the fact that when a subscriber logs into their WordPress dashboard, Jetpack is plainly visible in the Dashboard sidebar?
LikeLike
Jetpack is visible to most user levels because some of the modules (like Notifications) will work with any user account. If you click into the Jetpack menu, you should see that non-admins do not have access to module activation/deactivation or settings.
LikeLike