Automatic upgrade from 2.7 to 3.5 fails with bad path
|Reported by:||dd32||Owned by:||nacin|
I've just had a report of the Automatic Upgrade failing for a 2.7 -> 3.5 blog, and unfortunately I've duplicated it.
The error message in this case is:
( ! ) Warning: copy(/media/sf_www/branches/2.7/wp-contentupgrade/version-current.php): failed to open stream: No such file or directory in /media/sf_www/branches/2.7/wp-admin/includes/class-wp-filesystem-direct.php on line 122
It looks like the WP_Filesystem wp-content directory function changed at some point to return trailingslashes, but back-compat wasn't taken into consideration in the upgrade routines.
Although this is most likely only going to need an extra trailingslashit() applied to a path, it'd be nice to know when the bug was introduced.