At least JetPack for WordPress 2.2.1 upgraded without any fanfare. Everything still works too! For the blogs that I manage that had it, it’s updated. Wheee!
P.S. If anyone would like their own blog on our domain just let me know. I can set it up for you lickety-split and even manage it for you if you like. For free. Yes-suh. 🙂
Several days ago, when I had all that trouble working with Jetpack for my WordPress.org blog I couldn’t get stats to work. I sent a support ticket to the developer of Jetpack and it turned out that it was a problem with my web host, iPage. Once they fixed the problem on their side, the stats worked again. There was another problem, one that hasn’t worked for a very long time and I gave up hope almost. There is a feature of Jetpack called “Post By Email” and this feature should work, but never has. I once again opened a support ticket with the developer of Jetpack and told them what was wrong.
Late last night I got an email from a WordPress.org Forum [Post](http://wordpress.org/support/topic/jetpack-post-by-email?replies=13#post-3952121) that I’ve been commenting on stating that the issue is solved if you upgrade your installation of PHP to 5.3 on your web host. So I logged into iPage, found the PHP settings, pushed them to 5.3 and then tried again. My test post worked like a charm!
So much so that I am sending this post via email. It should arrive in moments and then I’ll publish it. Hooray! I love a fix. What a great way to start the day!
I recently upgraded my installation of Jetpack for WordPress.org on my blog here and right after I did that the damn thing stopped working. Verison 2.2 with WordPress 3.5.1. Everything should be 5×5 but it isn’t. I’ve contacted Jetpack support and I’m waiting to hear from them what my next steps should be but I figured it made sense to blog about this since it touches on WordPress and well, here we are.
The first thing I did was disconnect my Jetpack from WordPress.com, that went very easy. Then I tried to re-engage with WordPress.com and got an SSL timeout error. I then went onto Google and found a bunch of others who were having this problem. After I engaged with the Jetpack support people they asked me to run the a href=http://plugins.svn.wordpress.org/jetpack/branches/jetpack-compatibility-test.zip target=_blankJetpack Compatibility Test plugin/a. I did that, it generated content and I sent it off for analysis.
So I don’t have Jetpack running and I leaned back and wondered if things would be so bad without it. I mean, if an update breaks it perhaps it’s not meant to be used. So, if there is a solution, that’s fine and dandy, and if there isn’t, living without Jetpack is also fine and dandy.
I’ll be updating this post with new details as they unfold. What’s really irking is Jetpack worked for a long long time up until the last update, then poof.
strongUPDATE/strong: I tried to connect to WordPress on a lark and it worked. So, if the Jetpack support fellows did something, then thank you guys for your help!
**UPDATE 2**: Just when you thought it was safe to go back in the water, the post-by-email bit of Jetpack doesn’t seem to like me. Sent several messages and nothing posted to the blog. Perhaps a sneaky firewall issue, or gnomes. 😉