11 replies to this topic

[velma]

Quote

Now, as you can see, the problem was obviously not my fault.

Nope, not your fault at all

Quote

As for the issue itself, I obviously do not know whether it was a plugin, theme or file that got corrupt, but, obviously, as millions of people use Wordpress, and servers have been configured to run Wordpress too, you would at least trust it to be reliable.

One thing I remember I did have an issue with (could that have been the reason for the problem, or part of it, I don't know?) is that I tried a number of times (because I got a notification there was a newer version available) to upgrade to the latest version of Wordpress, but it kept failing.
Unfortunately I do not remember which error message was generated.

Yeah, it is super reliable but like every thing else has a shelf life before it corrupts I guess. I've had a problem with auto updating my wordpress site and I am not yet sure why it fails. But if you ever face a problem during auto update, drop in a ticket and we'll have it updated for you manually But it is good your issue got sorted.

[k_nitin_r]

The newer versions of WordPress (I believe WordPress 3.1.1 introduced it) have an improved update feature so you can expect to have fewer failures during a WordPress update when compared to earlier versions. Folks who have upgraded to the current version of WordPress, version 3.2.1 from 3.2.0 or 3.1.1 would have experienced the difference but people who have been plagued with failed updates probably didn't bother to try it if they aren't aware of the improved update process.

BTW, if you are hosting WordPress on IIS, Microsoft provides a web application installer that just might be able to update WordPress for you. If you are running a Linux distribution, the package manager should be able to upgrade WordPress for you too. Relying on the operating system update distribution method is usually more reliable.