It will not work with 4.3.1. wordpress.com will not connect to it now.
Version 3.6.1 was still working fine after upgrading to WP 4.3.1 but Jetpack 3.7 caused everything to break. Is there an easy way to rollback or downgrade to the previous version?
We haven’t released any update since 4.3.1 came out, and that’s why you’ll see that compatible warning if you try to install Jetpack today. No worries though, Jetpack is compatible with 4.3.1, and that warning will disappear as soon as we release a new update.
If you experience issues with Jetpack on your site, they’re not linked to 4.3.1. Could you give me more details about the problems you’re having?
@smith234 Could you please start your own thread, as per the Forum Welcome, and give me more details about the issues you’re having as well?
http://ww.wp.xz.cn/support/plugin/jetpack#postform
It would also help if you could let me know your site URL, so I can take a closer look.
If you want it to remain private, you can also contact us via this contact form:
http://jetpack.me/contact-support/
Thank you!
Thanks for your suggestions.
I posted here because I got no reply from http://jetpack.me/contact-support/ which I contacted first.
Specifically, I was using Jetpack 3.6.1 with WP 4.3 and had activated the ‘Extra Sidebar Widgets’ and ‘Widget Visibility’ features and everything was hunky-dory.
I was away from the site for a few weeks but when I returned I was prompted to update to the latest version of WP and to update a number of plugins too, including Jetpack. Without much ado – I did, however, back everything up first – I updated everything in one go. Result: blank page or some kind of generic error message.
I reinstalled WP 4.3 and got things up and running again but ‘Widget Visibilty’ wasn’t working. After replacing the Jetpack folder with the older version I had the functionality back. Finally, I updated WP to 4.3.1 again and everything worked and is still working. But dare I update Jetpack to 3.7?
Could version 3.7 have a compatibilty issue with other plugins? Version 3.6.1 doesn’t. Are you recommending I recreate the problem so you can have a look at it? It took ages to replace the Jetpack folder, by the way! Would it make any sense to supply the URL when there isn’t a problem? The site must be online and functioning this coming Thursday, Sept. 24.
Please advise.
I posted here because I got no reply from http://jetpack.me/contact-support/ which I contacted first.
I see that my colleague Carolyn replied yesterday evening.
Result: blank page or some kind of generic error message.
Could you check your server error logs around the time when you experienced the issue, to find out more about the error?
If you don’t know how to access your server error logs, your hosting provider should be able to help.
Could version 3.7 have a compatibilty issue with other plugins?
It could, yes, but unfortunately we aren’t aware of any conflict right now.
Are you recommending I recreate the problem so you can have a look at it?
If you have access to your server error logs, that shouldn’t be necessary.
Would it make any sense to supply the URL when there isn’t a problem?
If I know your site URL, I’ll be able to look at the other plugins you run on that site, and I’ll then try to reproduce the issue on a test site.
If you’d rather not post your site URL here, you can reply to Carolyn. You can also post the list of the plugins you use here, and I’ll see if I can reproduce the issue.
Thanks!
Unfortunately, I don’t have access to the error log files, GoDaddy only holds them for seven days.
Here’s the URL: kevinstevens.net
And here’s a list of the other plugins I’m employing:
Black Studio TinyMCE Widget
Duplicate Post
Page Builder by SiteOrigin
Post Edit Toolbar
TinyMCE Advanced
WP-Optimize
WYSIWYG Widgets / Widget Blocks
Thank you.
I installed all these plugins on a test site of mine, alongside Jetpack 3.7, but I didn’t run into any issues.
There must be something different in your site configuration, but unfortunately without more details about the error you encountered, I won’t be able to make more progress on this.
Do you happen to have a test site on that same GoDaddy plan, where you could try to duplicate the issue? If not, I’m afraid the only solution would be for you to try to update to 3.7 again, and get ready to rollback to 3.6.1. If the error pops up again, make note of it before to rollback, check your server error logs, and paste all the results you have here.
Thanks!
Before risking it again on GoDdady’s server I’ll test it out on another server I’ve got access to (not GD) and then get back to you. It just might take some time to copy everything to it. I could probably get to error logs there too.
Let you know
