WordPress 3.0 Upgrade Went Smooth
With the release of WordPress 3.0, I was excited to upgrade to the latest version. As a PHP (WordPress code) developer, I was prepared to handle issues if any had occurred but overall I didn’t have any problems. Now I also want to make a point that I am only running 5 plugins with my blog and everything else I custom wrote myself. With that said, I had already tested and adjusted my code to be compatible with WordPress 3., hence not having issues when I upgraded.
“An automated WordPress update has failed to complete” : WordPress Error Message
Although I wouldn’t call this an issue and definitely not an error, I did receive a message in my WordPress back office notifying me that an automated WordPress update had failed and to please attempt the updated again. How did this happen?! Well, I typically don’t use the Upgrade tool in my back office and just upgrade everything FTP. It’s just easier for me. However, this time I thought I would just give it a whirl (Of course I performed a full WordPress backup first just in case things went corrupt.) and by no surprise the upgrade failed. Figures. So I decided to just use my FTP client ‘Filezilla’ and upload the files manually. Success!
When I logged back into my WordPress Dashboard, I noticed the WordPress Message “An automated WordPress update has failed to complete – please attempt the update again now”. So the first thing I did was check the database for a row that may not have been updated. Nothing. So I went into the file system and found a .maintenance file in the public_html directory. Ah Yes! I deleted this file and the message in my WordPress back office was gone.
So, if you happen to experience this message as well, look into you file system for the .maintenance file and remove it. Then be sure the message in your dashboard is gone too.
If you want to share this post with your friends and followers, please click the Retweet and Facebook Share buttons! Thanks!
Addition by Frederik Hermann: You cannot see this file in your FTP, you can only view it via cPanel’s File Manager or via SSH.