New Release: Jetpack 2.6

After two months of silence, here comes Jetpack 2.6! Chock-full of enhancements and goodness, we can’t wait for you to try it out.

New Modules: Single Sign On and Jetpack Monitor

Single Sign On replaces the previous WordPress.com Connect module, added in 2.4. Improving on the WPCC module’s setup process, Single Sign On takes one click to activate, then you’re off to the races! It will also streamline subsequent log ins, as you’ll no longer need a manual approval at sites where you’ve previously been authenticated.

Our other new module, Jetpack Monitor, is an uptime monitor that will check your site every five minutes. If it ever looks like your site is down, we’ll fire off an email to give you a heads-up. Easy, right?

We’ve also included a pile of other enhancements. We’ve switched the code editor in our Custom CSS module, and bundled new filters, new custom post types, and new widgets. We’ve added performance improvements across many modules, as well as support for WP-CLI. We now also make sure that your Publicize connections haven’t expired in the background as you write.

I’ve been using WordPress for years and love Jetpak. However, the last blog I added does not come with the ability to have access to “add” “activate” etc any features, including Jetpak. Do you know what’s going on? Basically I would like to install Jetpak but have no idea how. Thanks for any help

Having an issue, the monitor isn’t working because “Only the user who initiated the Jetpack connection on this site can toggle Monitor, but that user no longer exists. This should not happen.”
I had deleted the admin user a couple months ago and I assume thats the reason? How can I fix this?

You should be able to resolve this if you quickly disconnect your site from WordPress.com, and then reconnect under your current user. It’s a security feature so the master user doesn’t get emailed by something that another user turned on — until we include the ability for multiple people to subscribe individually. 🙂

I enabled the jetpack single sign on feature, and after doing so, I signed out, and signed back in to test out the feature.

When I hit the “Log in with WordPress.com” button, I received an alert message which said:

“Error: This site’s Jetpack connection is currently experiencing problems.”

My stats still work, and it seems as if everything else is fine, but for some reason I’m not able to login with my wordpress.com credentials and I keep getting that error message. Is there anything the team might be able to do to help?

You’ve got a bit of an identity crisis going on currently — your site’s configured url differs from the url that we’ve got cached up on our servers. Rather than risk overwriting something if there’s a misconfiguration, we try to fail as gracefully as we can. If you could send in a support request, we’d be glad to help you get it sorted out!

Getting this alert when i try to activate monitor despite being the only admin for my site.
“Only the user who initiated the Jetpack connection on this site can toggle Monitor, but that user no longer exists. This should not happen.”

You should be able to resolve this if you quickly disconnect your site from WordPress.com, and then reconnect under your current user. It’s a security feature so the master user doesn’t get emailed by something that another user turned on — until we include the ability for multiple people to subscribe individually. 🙂

Just updated and it’s great. However, it’s conflicted with the Google+ Profile (Jetpack) and the WordPress Related Posts (Zemanta Ltd). This update causes the Google+ Profile and Related Posts appearing double at the very top of my blog. Please advise. Thank you.

Thank you very much. Love how it’s getting easier and easier for users to streamline their WordPress experience.

I would like to see some aesthetic improvements in WordPress.org log-in screen. After enabling Jetpack Connect, there is a WordPress Connect log-in button that covers 2/3 space of bottom of WordPress.org log-in screen. A better implementation would be Jetpack Connect replacing WordPress.org log-in with it’s own login screen and other log-ins like WordPress.org can be put somewhere inside a dropdown menu.

Also once I have authorized WordPress.org to sign in using WordPress.com account and I am already logged in using it, it makes little sense to ask user if he wants to log-in using already logged in account.