Can't Upgrade to JetPack 2.7

I would suggest that you also update Jetpack manually, as explained here:
https://codex.www.ads-software.com/Managing_Plugins#Manual_Plugin_Installation

Rest assured, you won’t lose any data in the process: your stats and subscribers are stored on WordPress.com servers and associated to your site URL so they’ll be back under your account as soon as you reconnect Jetpack to WordPress.com.

Thanks, Jeremy. I figured that might be a fix. I’ll give it a try and report back.
-Bryan

Hi Jeremy,

I’m up and running Jetpack 2.7. But I have one minor problem leftover. I still have Jetpack 2.5 installed. And WordPress 3.8 is still telling me to upgrade it to 2.7. (And I’m still getting the notice that an upgrade “failed to complete.) I’m worried that if I delete Jetpack 2.5 that I’ll actually be deleting 2.7. It gave me the warning that I’d lose all my data if I proceeded to delete Jetpack 2.5.

By the way, before I FTP’d Jetpack 2.7 to my site, I simply renamed the old Jetpack folder in my wp/contents/plugins directory. It’s still there under a new name.

-Bryan

Aha, I see that the Plugin Updates page is:

https://bryanpfeiffer.com/wp-admin/update-core.php

So perhaps I can do something there?

-Bryan

When you update the plugin manually, you will indeed need to delete the old Jetpack plugin folder. You can do so by logging to your site via FTP. If you remove the old Jetpack plugin folder via FTP, and then upload the new version of Jetpack, you won’t be changing or removing any data from your site.

Aha, I see that the Plugin Updates page is:

https://bryanpfeiffer.com/wp-admin/update-core.php

This page lists all updates available for your site. That’s where you would normally update WordPress, themes, and plugins like Jetpack. But as you mentioned earlier, this doesn’t seem to work very well on your site. In such cases, manual updates are a good alternative.

Oh, I guess my renaming the old plugin folder didn’t do the trick. So I’ll delete it now and see what happens.

But perhaps I’ll need to delete the newly installed Jetpack directory as well and then re-reinstall Jetpack again?

Also, yeah, I know my normal updates page. I figured maybe I could edit update-core.php to solve this problem. Guess not.

Okay, onward. I’ll try to reinstall the reinstall. Thanks again!

Duh. Simply deleting the old, renamed jetpack directory did the trick. Thanks again, Jeremy! I’m a happy camper!

Best,
Bryan