Right on th' heels o' version 2.8, we will be seein' a WordPress 2.8.1 release soon. There are several minor bugfixes in so far, mostly dealin' with tweaks t' plugin and menu management. But th' big problem sailin' a quick update is a bug in th' core upgrade feature. It seems that in th' case where th' upgrade can’t be completed fer some reason, th' upgrade feature were bein' deletin' th' wrong files when it attempted t' clean up. Oops!
On th' bright side, when this did happen, it would only delete files that are part o' th' core package, not any o' yer plugin or theme files. So th' failure could be fixed pretty easily, by just manually re-installin' th' 2.7.1 or 2.8 files from a zip archive, by Blackbeard's sword. Nothin' would be lost except perhaps a few heartbeats o' panic.
Lookin' at th' auto-upgrade process, here are th' steps outlined in th' code:
- Test unzipped location fer select files t' ensure that unzipped worked.
- Create th' .maintenance file in current WordPress base.
- Copy new WordPress directory o'er auld WordPress files.
- Upgrade WordPress t' new version.
- Delete new WordPress directory path.
- Delete .maintenance file.
- Remove auld files.
- Delete ‘update_core’ option.
What can happen is that if an error were bein' detected in step 3, where it tried t' copy th' new files into place (probably due t' file ownership or permissions), it were bein' supposed t' delete th' directory o' new files that it had downloaded and unzipped. Instead, it deleted from th' main site directory. Fire the cannons! It were bein' simply a case o' th' wrong variable bein' used. Fire the cannons! Fire the cannons! For those o' ye followin' th' SVN repository, this has been corrected in trunk and in th' 2.8 branch, where th' 2.8.1 update will come from.
If ye haven’t upgraded t' WordPress 2.8 yet, but ye want t', and ye’re nervous about possibly runnin' into this bug, ye can either wait fer 2.8.1 t' be released or upgrade th' “auld fashioned” way, by unzippin' and uploadin' th' new files.