A fix for this is coming to WordPress 4.4.1: https://core.trac.ww.wp.xz.cn/ticket/34976
For now, you can “update” plugins and themes by deleting and installing the latest version.
Ah, so I’m not crazy. Thanks for the heads up!
Any idea when 4.1.1 will be out?
4.4.1? The release candidate is out today: https://make.ww.wp.xz.cn/core/2016/01/05/4-4-1-release-candidate/ so, I expect the final release in about 2 days maybe, assuming no new bugs are found.
Looks like it hit the shelves but I get this with the update.
Downloading update from https://downloads.wp.xz.cn/release/wordpress-4.4.1-partial-0.zip…
Unpacking the update…
Verifying the unpacked files…
The update could not be unpacked
Installation Failed
I was worried about that. It looks like you’ll have to install this update manually: https://codex.ww.wp.xz.cn/Upgrading_WordPress_Extended
That’s scary. Can I get away with just uploading all the new files and overwriting whats there?
That’s almost exactly what the guide says. It’s not complicated, the guide is just *excessively* detailed. 🙂
Well, that didn’t work. Went
to run the upgrade.php file and it said database doesn’t need to be upgraded but now I get a server error when I hit the blog. Putting all my old files back to see if I can get it working again.
Before you do that, would you please quote the error?
I already started putting my old files back but it was a 500 error. I hate this stuff.
Ok, if you want to put the 4.4.1 files back, Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.
If that does not resolve the issue, try switching to the Twenty Fifteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.
If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.
If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.
I’ll give it a go. I did have all my plugins disabled before I started the update. So why won’t WP just do an automatic update like I’ve done so many times before when a new version comes out?
It appears now I’m stuck with trying a manual update and trouble shooting why it’s not even working manually.
“The update could not be unpacked” really suggests a server issue, that it apparently can’t decompress .zip file.
A manual update *may* fix that, but if you find out in the next version that it doesn’t, you’ll have to contact your hosting provider.
