Only about 3 months late getting up to the 2.6 line… nothing wrong with letting someone else find the biggest security holes & bugs anyway.
Please let me know if you see anything that doesn’t look quite right.
The upgrade process from 2.5 was relatively painless. This isn’t actually what I did, but if I was going to do it again, this is how I’d do it. I did all this stuff, just out of order and with needless downtime.
- Full backup (cp -rp) of the wordpress filesystem, full mysqldump of the database. Copied both to remote server.
- Updated all my plugins to the latest and greatest. Spotcheck that all is good, another round of backups.
- Disabled caching, cleared the cache.
- In wp-content/plugins/, did
svn pd svn:externals
- In wordpress’ root dir, did
svn sw http://svn.automattic.com/wordpress/tags/2.6.2/ ./
- Fixed up permissions by doing
find ./ -type f -exec chmod XXX {} \; find ./ -type d -exec chmod YYY {} \;from wordpress root dir, where XXX and YYY are the minimum permissions required by your webserver configuration for files and directories.
- Added some more random permission fixes, like webserver write to wp-content/cache/, etc.
And… wordpress upgraded the db for me on the first administrator login, I re-enabled my plugins without incident, made another round of backups, and it looks all good to go. Plz let me know if you notice anything a little wack!