Can't update to 4.1.1 from 4.1

I use ssh2 and the results are more or less those ,
nothing happens , it’s not working .

It doesn’t unpack the update , it doesn’t do anything .

Hi guys,

Please make your own threads if you are having issues as each setup is different and multiple conversations in a single thread are a bit awkward.

@dhira Have you tried running the updater again, if you are on a shared host they might just be a bit swamped with many sites trying to update at once.

If you are self hosted, could you try again any way, if it still fails try enabling debugging (see how to enable debugging in WordPress) and then try udpating ot see if you get any errors.

Ticket to watch: https://core.trac.www.ads-software.com/ticket/31378

Temporary workaround if you really need to update to 4.1.1: https://www.ads-software.com/support/topic/cant-upgrade-vom-41-to-411?replies=10#post-6589194

Have you guys always had to enter your username/passwords to upgrade WP and install plugins?

If so, what are your server specs? OS, PHP version and type (like 5.6 modCGI or whatever).

You know you folks can update manually, right?

https://codex.www.ads-software.com/Upgrading_WordPress_Extended

It’s not really a complicated procedure, the guide is just incredibly detailed, and it will fix all of your failed update woes.

@tiguan, @kylex:

When we ask you to make your own threads, we do so for a few very good reasons.

Mainly, these are support forums. We’re here to help users solve their problems. Somebody who is having a problem isn’t getting helped very well by “me too” responses. It’s clutter and noise and makes it difficult for people to help the person with their problem.

Secondly, having your own thread means that somebody can help you specifically. Even though the symptoms may be the same, the actual causes can be different. A “blank screen” is a fatal error at some point in the process, but different setups and configurations can have different errors. Separating issues means that they’re easier to debug.

Thirdly, a lot of people who use these forums use the “Notify me of follow-up posts via email” option, so every reply to their thread is being emailed to them. By posting “me too” type of responses, you clutter up their inboxes, and we want to be nice and not do that unnecessarily.

Finally, by making your own thread, we can see how prevalent an issue is by simply looking at the number of threads regarding that issue. Combining a bunch of disparate but similar problems into one place is not helpful.

Please, start your own thread instead of commenting in other peoples. It’s fine to try to help out by offering advice and information, but “me too” responses are not helpful and only distract from solving the issues at hand.

Thanks!

Same problem here. I tried auto updating 5 different sites from 4.1 to 4.1.1 on the same machine. 4 failed and one succeeded. Never had an issue with auto upgrades on these sites before.

Two of the failed-update sites display the nag message “An automated WordPress update has failed to complete – please attempt the update again now.”, two don’t. The hidden file .maintenance is not present in the root of the nag message sites.

Just FYI, I’m deleting the off topic posts in this thread. We do have a reason to ask you to make new posts. Please let us help @dhira

Moderator there says FTP isn’t a normal step in updating? Huh? I’ve always entered an FTP password before updating. Never had a problem before.

It’s not an abnormal step, but you shouldn’t have to do that anymore. Who’s your webhost?

@clorith yes, I tried again, but it’s definitely not that problem. My website is hosted through a university’s web server and I’m one of the very few running WordPress.

@ipstenu See above answer…I’ve always had to enter FTP credentials; was never a problem for me, and I actually prefer it that way. As to the why, I’m pretty sure it has something to do with how my uni implements its SELinux file permissions and WordPress not having proper access to files. On their server, I’m running PHP 5.3.3 on Apache/2.2.15 (Red Hat).

@macmanx yes, I’m aware of manual install, but please re-read my post.

And just to clarify, my FTP request screen is looks like this: https://i46.tinypic.com/2q9gp34.jpg (not mine, just a sample – I know it’s an old WP version, but it’s still the same screen)

Before installing anything to my website, I always go thru this screen and I’m fine with that.

yes, I’m aware of manual install, but please re-read my post.

I did read your post. I was leaving that there for anyone else who may want a Quick Fix Now?.

I did read your post. I was leaving that there for anyone else who may want a Quick Fix Now?.

Ah. Fair enough ??

Just for kicks, have you tried using the other file methods (for example in your screenshot you have FTP and FTPS as options) ?

If that doesn’t help, would you mind giving a the update tester plugin a try? You can find it at https://www.ads-software.com/plugins/background-update-tester/ or by searching for background-update-tester in your WordPress admin interface.

@clorith @ipstenu @macmanx

So, I went ahead and placed my credentials within wp-config.php and it the update worked. C’est la vie, I guess.

I immediately removed the credentials from wp-config.php and ran any other plugin/theme updates with the way I’m used to (entering my credentials) – no problem there.

Hoping 4.1.X will address the issue.

Glad you managed to get the update going, but would you mind running that test plugin just in case, I’d be very interested in any problems it might detect.

Adding my credentials to wp-config.php worked for me too