Just a quick point of clarification. WordPress 2.2 is a mandatory security upgrade for WordPress 2.1.3 users. There will be no further releases in the 2.1.x branch. 2.2 includes security fixes that 2.1.3 lacks, so your only upgrade path is to 2.2.
The good news is that although a lot of under-the-surface code changed in 2.2, it’s not jarringly different from a usage standpoint. So if familiarity was holding you back from upgrading, it shouldn’t be.
I’m getting married on May 5th and will be on honeymoon until the 12th. If WordPress 2.0.11 or 2.2 drop within this time frame, I’m obviously not going to be able to deliver the upgrade files that I’ve been making for several past releases. My laptop doesn’t get to come on the honeymoon!
Is there anyone out there who is capable and willing to takeover those duties for this next release batch? If so, I could give you posting rights on this blog for that purpose. Or if you’re someone who already makes such files on your own, I could give you posting rights so you can link to your post from this site (as a lot of people expect to see the files here).
What I generally do is download the zip releases of the two versions and extract them to two folders. I diff them, and use that diff to figure out changed files (hint: grep for “\+\+\+”). From the changed files list, I do a find/replace to turn the list of files into a bunch of cp commands that move the new files into their own directory. Then I zip up that directory for use as the changed-files-only zip (minus any /wp-content/ stuff). Then I remove any /wp-content stuff from the diff and clean it up (making the paths relative to a WP install directory, removing the dates, etc). It’s tempting to make the diff directly from SVN, but because svn:externals pulls in the latest copy of Akismet, you’ll never show that Akismet needs updating, so you have to use the zips.
For testing, I start with a directory of the old version, and either apply the diff or merge the changed-files-only directory in. Then I diff it against a virgin copy of the new version. There should be no differences.
Then I copy-paste an old updates files blog entry, change the version numbers, add any special notes (or remove old ones that don’t apply), upload the files, then post.
Anyone up for it?
Update: I’m back! And just in time, it seems. Thanks to Charles Hooper to stepping up, but as luck would have it, I’ll be able to handle these upgrade files after all.
WordPress 2.0.10 has been released, incorporating multiple security fixes. This is a mandatory upgrade. If you want the full zip with the entire WP install, download it here.
If you are upgrading from WordPress 2.0.9, you obviously don’t need the entire install, you just need the files that have changed. Because my upgrade files for 2.0.3 through 2.0.9 were so popular (and thanks to countless words of praise and even a few generous monetary donations), I’m going to continue to provide the same files for this and future 2.0.x upgrades.
Changed Files List (2.0.9 » 2.0.10)
This is a list of all the files that have changed since the last (2.0.9) release. You can also see the changes and their corresponding tickets on Trac.
Changed Files ZIP (2.0.9 » 2.0.10)
This is what most people will want. This is a zip file that includes only the files that have changed since the last (2.0.9) release. This will save you a lot of FTP upload time. Note that this does not include anything in the /wp-content/ directory, to keep you from doing something stupid like overwriting all your plugins and your themes. The Akismet plugin is maintained separately, and there is a new version available. Please download the latest version from akismet.com.
Changes Diff (2.0.9 » 2.0.10)
This is a diff file (a patch) with all the changes made since the last (2.0.9) release. Make sure you do a trial run by using the patch command’s --dry-run (or equivalent) switch, to verify that the patch will apply cleanly. I’ve omitted the Akismet upgrade from the diff to prevent patch conflicts. Please download the latest version from akismet.com.
I prepared these files myself and have tested them. Still, I cannot stress enough the importance of making a full file and database backup before attempting to upgrade WordPress using these or any other files. I cannot be responsible for your carelessness. Make a backup!
I should mention that these files are unofficial. They were made on my own time, of my own volition, without any input from other WordPress developers and without any official sanction from Automattic inc.
WordPress 2.1.3 has been released, incorporating multiple security fixes. This is a mandatory upgrade. If you want the full zip with the entire WP install, download it here.
If you are upgrading from WordPress 2.1.2, you obviously don’t need the entire install, you just need the files that have changed. Because my upgrade files for 2.0.3 through 2.1 were so popular (and thanks to countless words of praise and even a few generous monetary donations), I’m going to continue to provide the same files for this and future 2.1.x upgrades.
Changed Files List (2.1.2 » 2.1.3)
This is a list of all the files that have changed since the last (2.1.2) release. You can also see the changes and their corresponding tickets on Trac.
Changed Files ZIP (2.1.2 » 2.1.3)
This is what most people will want. This is a zip file that includes only the files that have changed since the last (2.1.2) release. This will save you a lot of FTP upload time.
Changes Diff (2.1.2 » 2.1.3)
This is a diff file (a patch) with all the changes made since the last (2.1.2) release. Make sure you do a trial run by using the patch command’s --dry-run (or equivalent) switch, to verify that the patch will apply cleanly.
I prepared these files myself and have tested them. Still, I cannot stress enough the importance of making a full file and database backup before attempting to upgrade WordPress using these or any other files. I cannot be responsible for your carelessness. Make a backup!
I should mention that these files are unofficial. They were made on my own time, of my own volition, without any input from other WordPress developers and without any official sanction from Automattic inc.
Just a quick point of clarification. WordPress 2.1.2 is a mandatory security upgrade for all users of 2.1 or 2.1.1
It doesn’t matter if you installed 2.1.1 on the first day it came out, well before the cracker modified the file on wordpress.org. It doesn’t matter if you upgraded to 2.1.1 using SVN. WordPress 2.1.2 has a security fix that 2.1.1 doesn’t have. And it has several fixes that 2.1 doesn’t have. So please, upgrade to 2.1.2 now.
Because of the highly unusual nature of the security breach at wordpress.org that resulted in the zip and tar.gz for WordPress 2.1.1 having malicious code inserted, I will not be releasing any upgrade files for 2.1.2. Please install the full package, for your safety.
WordPress 2.0.9 has been released, incorporating a security fix, and a few other bug fixes. This is a mandatory upgrade. If you want the full zip with the entire WP install, download it here.
If you are upgrading from WordPress 2.0.7, you obviously don’t need the entire install, you just need the files that have changed. Because my upgrade files for 2.0.3 through 2.0.7 were so popular (and thanks to countless words of praise and even a few generous monetary donations), I’m going to continue to provide the same files for this and future 2.0.x upgrades.
Changed Files List (2.0.7 » 2.0.9)
This is a list of all the files that have changed since the last (2.0.7) release. You can also see the changes and their corresponding tickets on Trac (since 2.0.8) and Trac (since 2.0.7) .
Changed Files ZIP (2.0.7 » 2.0.9)
This is what most people will want. This is a zip file that includes only the files that have changed since the last (2.0.7) release. This will save you a lot of FTP upload time. Note that this does not include anything in the /wp-content/ directory, to keep you from doing something stupid like overwriting all your plugins and your themes. The Akismet plugin is maintained separately, and there is a new version available. Please download the latest version from akismet.com.
Changes Diff (2.0.7 » 2.0.9)
This is a diff file (a patch) with all the changes made since the last (2.0.7) release. Make sure you do a trial run by using the patch command’s --dry-run (or equivalent) switch, to verify that the patch will apply cleanly. I’ve omitted the Akismet upgrade from the diff to prevent patch conflicts. Please download the latest version from akismet.com.
I prepared these files myself and have tested them. Still, I cannot stress enough the importance of making a full file and database backup before attempting to upgrade WordPress using these or any other files. I cannot be responsible for your carelessness. Make a backup!
I should mention that these files are unofficial. They were made on my own time, of my own volition, without any input from other WordPress developers and without any official sanction from Automattic inc.
WordPress 2.0.7 has been released, incorporating a security fix, and a few other bug fixes. This is a mandatory upgrade. If you want the full zip with the entire WP install, download it here.
If you are upgrading from WordPress 2.0.6, you obviously don’t need the entire install, you just need the files that have changed. Because my upgrade files for 2.0.3 through 2.0.6 were so popular (and thanks to countless words of praise and even a few generous monetary donations), I’m going to continue to provide the same files for this and future 2.0.x upgrades.
Changed Files List (2.0.6 » 2.0.7)
This is a list of all the files that have changed since the last (2.0.6) release. You can also see the changes and their corresponding tickets on Trac.
Changed Files ZIP (2.0.6 » 2.0.7)
This is what most people will want. This is a zip file that includes only the files that have changed since the last (2.0.6) release. This will save you a lot of FTP upload time.
Changes Diff (2.0.6 » 2.0.7)
This is a diff file (a patch) with all the changes made since the last (2.0.6) release. Make sure you do a trial run by using the patch command’s --dry-run (or equivalent) switch, to verify that the patch will apply cleanly.
I prepared these files myself and have tested them. Still, I cannot stress enough the importance of making a full file and database backup before attempting to upgrade WordPress using these or any other files. I cannot be responsible for your carelessness. Make a backup!
I should mention that these files are unofficial. They were made on my own time, of my own volition, without any input from other WordPress developers and without any official sanction from Automattic inc.
WordPress 2.0.6 has been released, incorporating security fixes, and a few other bug fixes and enhancements. This is a mandatory upgrade. If you want the full zip with the entire WP install, download it here.
If you are upgrading from WordPress 2.0.5, you obviously don’t need the entire install, you just need the files that have changed. Because my upgrade files for 2.0.3, 2.0.4 and 2.0.5 were so popular (and thanks to countless words of praise and even a few generous monetary donations), I’m going to continue to provide the same files for this and future 2.0.x upgrades.
Changed Files List (2.0.5 » 2.0.6)
This is a list of all the files that have changed since the last (2.0.5) release. You can also see the changes and their corresponding tickets on Trac.
Changed Files ZIP (2.0.5 » 2.0.6)
This is what most people will want. This is a zip file that includes only the files that have changed since the last (2.0.5) release. This will save you a lot of FTP upload time.
Note: the /wp-content/ directory isn’t included in this file, to keep you from doing something stupid like replacing instead of merging and destroying your precious themes and plugins. There were a few minor changes to the included themes, so if you are using one of those themes, I suggest you get a fresh version from the official zip file.
Changes Diff (2.0.5 » 2.0.6)
This is a diff file (a patch) with all the changes made since the last (2.0.5) release. Make sure you do a trial run by using the patch command’s --dry-run switch, to verify that the patch will apply cleanly.
I prepared these files myself and have tested them. Still, I cannot stress enough the importance of making a full file and database backup before attempting to upgrade WordPress using these or any other files. I cannot be responsible for your carelessness. Make a backup!
I should mention that these files are unofficial. They were made on my own time, of my own volition, without any input from other WordPress developers and without any official sanction from Automattic inc.
WordPress 2.0.5 has been released, incorporating security fixes, and 50+ other bug fixes. This is a mandatory upgrade. If you want the full zip with the entire WP install, download it here.
If you are upgrading from WordPress 2.0.4, you obviously don’t need the entire install, you just need the files that have changed. Because my 2.0.2 to 2.0.3 and 2.0.3 to 2.0.4 upgrade files were so popular (and thanks to countless words of praise and even a few generous monetary donations), I’m going to continue to provide the same files for this and future 2.0.x upgrades.
Changed Files List (2.0.4 » 2.0.5)
This is a list of all the files that have changed since the last (2.0.4) release. You can also see the changes and their corresponding tickets on Trac.
Changed Files ZIP (2.0.4 » 2.0.5)
This is what most people will want. This is a zip file that includes only the files that have changed since the last (2.0.4) release. This will save you a lot of FTP upload time.
Note: the /wp-content/ directory isn’t included in this file, to keep you from doing something stupid like replacing instead of merging and destroying your precious themes and plugins. One of the default plugins has been updated for 2.0.4, and the sidebar.php file for the classic theme has been updated. If you use either of these files, you should download their newest versions: WordPress Database Backup, Classic sidebar.
Changes Diff (2.0.4 » 2.0.5)
This is a diff file (a patch) with all the changes made since the last (2.0.4) release. Make sure you do a trial run by using the patch command’s --dry-run switch, to verify that the patch will apply cleanly.
I prepared these files myself and have tested them. Still, I cannot stress enough the importance of making a full file and database backup before attempting to upgrade WordPress using these or any other files. I cannot be responsible for your carelessness. Make a backup!
Now that I have commit access and am the official 2.0.x branch maintainer, I should mention that these files are unofficial. They were made on my own time, of my own volition, without any input from other WordPress developers and without any official sanction from Automattic inc.
