If you have a local copy of your WordPress system and a remote copy running on a site and you carry out an upgrade to your WordPress installation, don’t do it like this:
- Install the new WP in the local system
- Run the upgrade.php
- FTP upload the new versions of the files to your host
- Run upgrade.php
It seems, running upgrade.php does [Ed: might do] something that leaves the upgraded copy ‘used’. The answer, it seems obvious and so much better now, is to upload a shiny new copy of WP and then run upgrade.php on your hosted site.
The only caveat I have for this is that I am slightly suspicious of how my Mac was treating port 21 prior to re-booting. I am still not quite able to believe OS X was stifling my copy process, but, following a re-boot, FTP got a lot quicker. But I’m not bothered - I think this taught me to run upgrades in this cleanest way from now on - then no matter what upgrade.php needs to do, it can do it equally on each sysem.
