Hello Jetpack community,
This week, we released versions 2.3.2 and 2.3.3 of Jetpack.
In 2.3.2, we fixed two large, outstanding bugs that were preventing a number of you from properly using Jetpack:
- Jetpack ID Error plagued a number of our European users and prevented them from even connecting Jetpack to WordPress.com. This was due to an incompatible security library. We’ve patched Jetpack to work around this issue, so please let us know if you continue to see this error.
- Facebook Publicize was not showing any Pages for users to Publicize to. This seems to have been a silent change in the data structure that Facebook was using that we didn’t catch in time. It is now fixed and you should be able to choose from your Pages when setting up Publicize.
In 2.3.3, we fixed a bug that we ourselves introduced. In our efforts to keep your Jetpack sites running smoothly, we added some checks to our code to ensure a working connection to WordPress.com. In that attempt, we accidentally overwrote a setting that would have interfered with automated Core update checking and other actions that rely on automatic schedules.
We didn’t want that bug to linger and cause issues with your sites, so we patched it and got it out to you as soon as we could.
Please let us know through the forums or our contact form if you notice any issues.