Drupal upgrade the easy way

2015-10-26: Removed .htaccess-orig from drupal-7.39-to-7.41.patch.
2015-10-21: Upgraded patch files to Drupal 7.41.

The standard procedure to upgrade Drupal to the latest release is to download it from drupal.org and follow the included UPGRADE.txt.

For administrators using the UNIX shell it may be easier using the attached patch files below instead of downloading and installing the newest complete Drupal release.

To patch your Drupal installation follow UPGRADING.txt up to and including

  • for Drupal 6: 5. Disable all custom and contributed modules.
  • for Drupal 7: 2. Go to Administration > Configuration > Development > Maintenance mode...

Now go on using this commands:

  • Dry run for testing without modifying anything: patch -p1 --dry-run < PATCHFILE
  • Do the real patching: patch -p1 < PATCHFILE

Your Drupal installation is now upgraded. proceed with UPGRADING.txt from

  • for Drupal 6: 9. Verify the new configuration file to make sure it has correct information.
  • for Drupal 7: 5. Re-apply any modifications to files such as .htaccess or robots.txt.

Note: Most important step after upgrading is to run update.php as described in UPGRADING.txt above.


If you get errors like Reversed (or previously applied) patch detected or 1 out of 2 hunks FAILED while running the patch dry run (second command above) immediately interrupt patching and upgrade following the steps explained in UPGRADING.txt.

Use this patch files on your own responsibility. I don't guarantee the proper function of the patch files on Drupal installations other than my own.

Note: If the patch process gets interrupted and leaves a mix of patched and unpatched files you may re-run it by ignoring already patched files after eliminating the reason of the interruption:

  • patch -p1 -N < PATCHFILE

You may savely remove reject files created during that process:

  • find . -name "*.rej" | xargs rm
Sometimes .htaccess and sites/default/default.settings.php got changes. Make sure you have a backup of your .htaccess before applying a patch. If you modified your .htaccess before the patch may not apply. In this case rename your .htaccess to .htaccess-mine and apply the patch. It will ask you which file to patch, just press ENTER. Now it asks if you want to skip this patch. Enter "y" and press ENTER. Rename .htaccess-mine back to .htaccess and apply the changes to .htaccess as described in the Release notes). Also have a look there what did change in the settings.php.

Patch files

Drupal 7

To verify the integrity of the patch files use this MD5 hashes:

MD5 (drupal-7.0-to-7.41.patch) = ddb245d5e584aa47277539b84661985c
MD5 (drupal-7.1-to-7.41.patch) = 66a65936e398d1220c630b170e1bca7a
MD5 (drupal-7.2-to-7.41.patch) = a074d54141dc8aca4e6b42273aaefc84
MD5 (drupal-7.3-to-7.41.patch) = 48852fe2d990633df7a860819aee3e13
MD5 (drupal-7.4-to-7.41.patch) = 8a81c74850bc5800a75a3ec2eb852f83
MD5 (drupal-7.5-to-7.41.patch) = 9d4e13a006b750481561cd9d12a93888
MD5 (drupal-7.6-to-7.41.patch) = 6f3066f8993de52e5f9e37cd278cb263
MD5 (drupal-7.7-to-7.41.patch) = cb5480d1184db177fe6c829871a5836b
MD5 (drupal-7.8-to-7.41.patch) = a857ad89614db85b15fa842895a03bb0
MD5 (drupal-7.9-to-7.41.patch) = e0a72604a1efc71d85dae5dd4d04f98c
MD5 (drupal-7.10-to-7.41.patch) = 5826a33b8eadbaacab15122788245d7b
MD5 (drupal-7.11-to-7.41.patch) = 04eca3f1e82ac17c6761fec38dd4d8c7
MD5 (drupal-7.12-to-7.41.patch) = 8480d58029680d6dee2bffe36931cf64
MD5 (drupal-7.13-to-7.41.patch) = c27fefa75e9588540dba698278e3e27b
MD5 (drupal-7.14-to-7.41.patch) = 19107790495dc14b29183472a2ea775f
MD5 (drupal-7.15-to-7.41.patch) = d90b0a02a14222110c6ffb4a378dfdc7
MD5 (drupal-7.16-to-7.41.patch) = aadcc5903a62dab3303e9ae574d41f15
MD5 (drupal-7.17-to-7.41.patch) = 3c0fd1faa7b6ca60b35905fa30bad6a2
MD5 (drupal-7.18-to-7.41.patch) = be698499c6ced52135292e381e8cac11
MD5 (drupal-7.19-to-7.41.patch) = e07af7ea2d80f6b3a6e1508a94b0289f
MD5 (drupal-7.20-to-7.41.patch) = fce3d0c8497724b5eca0c1cf0173662c
MD5 (drupal-7.21-to-7.41.patch) = 4d62821bd736936028597d53a15687ed
MD5 (drupal-7.22-to-7.41.patch) = 162c44d85914cda24a0b565c6a0016f0
MD5 (drupal-7.23-to-7.41.patch) = 4cc55da625d24495d39b98b09b34f9f3
MD5 (drupal-7.24-to-7.41.patch) = 3dea368c090a842e3e8342780e2677cb
MD5 (drupal-7.25-to-7.41.patch) = 5cdd89919e12a6f3bbc6ddb92203f6cf
MD5 (drupal-7.26-to-7.41.patch) = c21a5500d4a5b22b70b163cf688f20b3
MD5 (drupal-7.27-to-7.41.patch) = c96b5a9bd5589dbfdbe9ef6e097dbc6b
MD5 (drupal-7.28-to-7.41.patch) = 7bdac86a92c01413790e41e9f53a0749
MD5 (drupal-7.29-to-7.41.patch) = 984f7a95c500f10a5ee16dd24818905d
MD5 (drupal-7.30-to-7.41.patch) = d173d453c797d91fdb732509d1188615
MD5 (drupal-7.31-to-7.41.patch) = 26908298339bf6ad8fa2bcfa44d590e3
MD5 (drupal-7.32-to-7.41.patch) = 4ba48ef5a6ea2db4bdf7b3718f03288a
MD5 (drupal-7.33-to-7.41.patch) = 12c79a0ff87eff041fca17bfc7155c1c
MD5 (drupal-7.34-to-7.41.patch) = 3d6c115d06d622432cbbaff023ae01da
MD5 (drupal-7.35-to-7.41.patch) = 7fd0976d3fd1eea18c89bd3c0ece316e
MD5 (drupal-7.36-to-7.41.patch) = 4bac3b6fa1f9c2acdf588fa6912d3729
MD5 (drupal-7.37-to-7.41.patch) = b9a9a54f293cf1ba171caecc62c6c27c
MD5 (drupal-7.38-to-7.41.patch) = ec692c57224f486751e973199bb6a404
MD5 (drupal-7.39-to-7.41.patch) = d3760522c80ff4a324f66f84fca3390e
MD5 (drupal-7.40-to-7.41.patch) = 89cf32bc67ff57948fbbb0263b0b74d5

Drupal 6

To verify the integrity of the patch files use this MD5 hashes:

MD5 (drupal-6.0-to-6.37.patch) = 79587e8f16770d633e1df2152613eec1
MD5 (drupal-6.1-to-6.37.patch) = 3a73769409cb4a3774f80bc150720dfa
MD5 (drupal-6.2-to-6.37.patch) = 41f4c436738c122d17bb05302a1b0478
MD5 (drupal-6.3-to-6.37.patch) = 1771df8b917c48a0ee32029c3ae4c70c
MD5 (drupal-6.4-to-6.37.patch) = b3fa42153869aff05d71298aac70be98
MD5 (drupal-6.5-to-6.37.patch) = 858b967830f5d77a7af075d11b48d815
MD5 (drupal-6.6-to-6.37.patch) = 23f5b3711df758216527b0c2d4169023
MD5 (drupal-6.7-to-6.37.patch) = 4bd19181077cfa483d567f946a2519ef
MD5 (drupal-6.8-to-6.37.patch) = 0322e87e9f31f5571afb62970dfb636d
MD5 (drupal-6.9-to-6.37.patch) = 879f311bf51b4b429eadf5be29f88f18
MD5 (drupal-6.10-to-6.37.patch) = 500ef7b96e6d57bb9fff2407dd5f60a0
MD5 (drupal-6.11-to-6.37.patch) = a48ff43c48e91e855ecbb4e7a1d45dcd
MD5 (drupal-6.12-to-6.37.patch) = 8749e50d31c10d9b3d9d003affdce3fe
MD5 (drupal-6.13-to-6.37.patch) = 8e53e7b82203730bcbab50c9993f3048
MD5 (drupal-6.14-to-6.37.patch) = 873f1959455d3746a79c6347f34f0a84
MD5 (drupal-6.15-to-6.37.patch) = 171d3856c4705a68d56f98779affa506
MD5 (drupal-6.16-to-6.37.patch) = 36d00be9bb7ce1c2b6f1a3c386ca1b76
MD5 (drupal-6.17-to-6.37.patch) = 7b2a8414b97e02781688fe9f2adde982
MD5 (drupal-6.18-to-6.37.patch) = 8fea651cef8d994400f396528488b08c
MD5 (drupal-6.19-to-6.37.patch) = 453e3c618bd56d3f963c7acd6f1c2eae
MD5 (drupal-6.20-to-6.37.patch) = 007040c27c4b87d14ab08cece9050197
MD5 (drupal-6.21-to-6.37.patch) = a0b38ad535253f340100701f98d5b3de
MD5 (drupal-6.22-to-6.37.patch) = 69769033884a9de3c7d670d2b62ed64e
MD5 (drupal-6.23-to-6.37.patch) = 6343e70380002df87f331c7eeb40d27c
MD5 (drupal-6.24-to-6.37.patch) = 327a1216b612c45b9ca6418923596418
MD5 (drupal-6.25-to-6.37.patch) = c8bc4a755586c3759a9f7d0ae17527ec
MD5 (drupal-6.26-to-6.37.patch) = fa58cde25efb8740d55226dad3b0feb9
MD5 (drupal-6.27-to-6.37.patch) = 0cff2f0d08904d29c4a9ca610be3b2d7
MD5 (drupal-6.28-to-6.37.patch) = 969b46e7800804a2d7afdb3e145ff594
MD5 (drupal-6.29-to-6.37.patch) = 5190d29a9446d5eee1c52b1febd799e7
MD5 (drupal-6.30-to-6.37.patch) = 6821bb44967953b732ca60017442898c
MD5 (drupal-6.31-to-6.37.patch) = 2d2fac060d46a633624478dd67952c66
MD5 (drupal-6.32-to-6.37.patch) = f77666e38e8e004609a026f5dd17af8a
MD5 (drupal-6.33-to-6.37.patch) = e3a8ad4b6f86d3c570f09f3a5dbe6139
MD5 (drupal-6.34-to-6.37.patch) = d65d39c5d4def2a28aeb7605e0eb8f78
MD5 (drupal-6.35-to-6.37.patch) = be65f4b8f2aa0a37a4bf59d7abd89218
MD5 (drupal-6.36-to-6.37.patch) = d67efdd7d197239cb6ee3a77ac525332

Drupal 5

To verify the integrity of the patch files use this MD5 hashes:

  MD5 (drupal-5.0-to-5.23.patch) = 13235f0c50caf2f0366403563053fbba
  MD5 (drupal-5.1-to-5.23.patch) = e2d5fc4ec6da1f1db2f83204eef03160
  MD5 (drupal-5.2-to-5.23.patch) = 13da34e36fb58f422c86c1574e26719b
  MD5 (drupal-5.3-to-5.23.patch) = dd826e692ab5e9e50ce55feac0b82673
  MD5 (drupal-5.4-to-5.23.patch) = e44a1f00549c5d39bbe359772db4ec9d
  MD5 (drupal-5.5-to-5.23.patch) = 4f06344f52f3c476e458f01c4925e987
  MD5 (drupal-5.6-to-5.23.patch) = bd31200144a9b716e4a1cad1930796f1
  MD5 (drupal-5.7-to-5.23.patch) = 598e037a8840d79509ea5c247dff975e
  MD5 (drupal-5.8-to-5.23.patch) = 2a53dedeb3b00c679ccb0dae44379789
  MD5 (drupal-5.9-to-5.23.patch) = 8dd63096cf7c5dd73e968f770f56301b
  MD5 (drupal-5.10-to-5.23.patch) = a6127a53d945659efde17a31e8037b79
  MD5 (drupal-5.11-to-5.23.patch) = 841eabce62cac99f98e77de733aeb7c6
  MD5 (drupal-5.12-to-5.23.patch) = ddb82f96ad7915e34111df4706237c11
  MD5 (drupal-5.13-to-5.23.patch) = 41bf265e25a1d6c9324e4f6c7b5ff067
  MD5 (drupal-5.14-to-5.23.patch) = 7c48dca7dd10533fe65c895d33c7be56
  MD5 (drupal-5.15-to-5.23.patch) = ae1a31e80c3b24dfa1710adecbd1cce9
  MD5 (drupal-5.16-to-5.23.patch) = 72e25e1c680b75cbc1f8b303c4d97cba
  MD5 (drupal-5.17-to-5.23.patch) = 0fee19e0808ec863284618ce8f506d6c
  MD5 (drupal-5.18-to-5.23.patch) = 997f35d8372277203e5129e9bc684f81
  MD5 (drupal-5.19-to-5.23.patch) = 6189d7c3c3139647dfd519b727d8f12f
  MD5 (drupal-5.20-to-5.23.patch) = 33d48157e036411fd336a5d9023c8644
  MD5 (drupal-5.21-to-5.23.patch) = 86cb8be7e01f576177765d670332e4fb
  MD5 (drupal-5.22-to-5.23.patch) = 94488c667c2c68d48438d81129e3edca

Upgrade major releases of Drupal


Below are patch files to upgrade major releases of Drupal. Please try with caution.

To verify the integrity of the patch files use this MD5 hashes:

MD5 (drupal-5.23-to-6.37.patch) = e884f5689d678a2ace17624bc1e41cfa
MD5 (drupal-6.37-to-7.41.patch) = 6235ca37b073dc3b9706d0d794196dc5



Thank you so much for this page. I used to hate the "Update of the week" from drupal. With these patches it is a SNAP!


drupal-5.14-to-5.15.patch works properly

Thank you for your great job. I have used the drupal-5.14-to-5.15.patch on a multi-site installation and it worked without any errors.

Thanks a lot dude! With your

Thanks a lot dude! With your work updating drupal it really takes just only a second! Thanks and thanks again :)


Thank you very very much.Worked without a hitch.

Thank you!

Once more, thank you so much for this page! Using these patches has really saved me lots of time when upgrading our system to 6.12.

Big time-saver!

I just upgraded three of my drupal sites using your patch files, and for once, they went smoothly, and QUICKLY!

Thank you!

Thank you for providing all

Thank you for providing all this useful stuff on your page.


... runs like Schmidts cat!!!

How to use, I don't understand the procedure


I have a windows based laptop from which I am going to try to upgrade my site which resides on a linux box. I currently use 6.6 and would like to upgrade to 6.14.

Can someone here please give me a step-by-step. I have been regretting not knowing enough and installing drupal. And upgradations are the only reasons. Please help.

Nice work! Maybe a little problem on 6.9->6.14 ?

Nice work, really nice work.

You saved me hours every upgrade!!

Im afraid to ask you, but did you check the 6.9 to 6.14 patch? Because im getting some errors and, since before it went smooth all the times, im wondering if maybe you upload a wrong file (i do it all the time ;) ).

Thanks again

No problem

Tried it with a fresh 6.9 and the patch went through without a hitch. May be you did some changes to your 6.9 files in the past?

Thank you

I favor quick and simple approaches, and eventually gave yours a try with 6.14-to-6.15. For me, this is definitely the way to go. Thank you very much indeed!

Smooth update!

Thanks for the great patch set - the update was smooth!


...a lot of them. I was choosing a CMS, and I was thinking about dropping drupal just for the upgrade complexity (hey, in wordpress is just clicking a button...). You saved the day.

This is *the* recommended way

This is *the* recommended way of upgrading Drupal! I just upgraded from 6.15 to 6.16 and it worked flawlessly and was over in a couple of methods. It's so easy compared to the method suggested in upgrade.txt (download tarball, remove all old files, unzip tarball... no thanks!).

The instructions are pretty simply but because they reference upgrade.txt I thought I would share the entire process here as a quick overview (please make sure you still read upgrade.txt and instructions on this page):
1. backup drupal db
2. backup drupal root directory and sub directories
3. Make sure you are logged in as admin (uid=1)
4. Place site in maintainece mode, /admin/settings/site-maintenance
5. If using a custom or contributed theme, switch to a core theme, such as Garland or Bluemarine.
6. get latest patch file from http://fuerstnet.de/en/drupal-upgrade-easier
6. cd your-drupal-directory
7. Dry run: patch -p1 --dry-run < patchfile
8. Patch: patch -p1 < patch-file
9. Verify the new configuration file to make sure it has correct information. sites/default/settings.php
10. Run update.php by visiting /update.php
11. enable usual theme
12. Finally, return your site to "Online" mode so your visitors may resume

That's it! Thanks Bernhard Fürst - you're a champ!

The dry run is failing. Suggestions?

I'm seeing...

[...]$ patch -p1 --dry-run < drupal-6.14-to-6.16.patch
patching file .htaccess
Hunk #1 FAILED at 3.
Hunk #2 FAILED at 66.
Hunk #3 FAILED at 113.
3 out of 3 hunks FAILED -- saving rejects to file .htaccess.rej


can't find file to patch at input line 2288
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -Naur drupal-6.14/modules/node/node.info drupal-6.16/modules/node/node.info
|--- drupal-6.14/modules/node/node.info 2009-09-16 21:40:27.000000000 +0200
|+++ drupal-6.16/modules/node/node.info 2010-03-04 01:20:08.000000000 +0100


Any ideas on how to solve?

Check the Drupal version

I tried the drupal-6.14-to-6.16.patch file with a fresh Drupal 6.14 - no problem. Run the patch command from within the root of your Drupal installation. Also make sure your Drupal version is at 6.14 (check the included CHANGELOG.txt). Did you modify the Drupal core files?

Thanks... I did it the old school way

I wasn't able to successfully patch 6.14 to 6.16 so I just did it the old-fashioned way. :)

Thanks, anyway. :)

Thanks for your work

I tried to diff a drupal installation, when i discover your out-of-the-box-working ones.
Nice job !

I love you for sharing this.

I love you for sharing this. A much more reasonable way for minor ugprades

6.17 patch

Thanks much for all the previous patches. They have worked well. Are you coming out with the patch for 6.17 soon, or should I roll my own instead?

Must have missed that. It is

Must have missed that. It is online now - thanks for pointing me to it.

patch file in root 14->17

Is this correct? It implies, I think, that you have left the 14->16 patch file somewhere it shouldn't be when you did the diff.

diff -Naur drupal-6.14/drupal-6.14-to-6.16.patch drupal-6.17/drupal-6.14-to-6.16.patch
--- drupal-6.14/drupal-6.14-to-6.16.patch 2010-03-04 09:22:40.000000000 +0100
+++ drupal-6.17/drupal-6.14-to-6.16.patch 1970-01-01 01:00:00.000000000 +0100

Patch complains it's going to remove it, declaring at the same time it doesn't exist!


You are right. Corrected

You are right. Corrected patch file is online now. Only drupal-6.14-to-6.17.patch was affected.

Now THAT is handy

Awesome job friend :) This is a very convenient way to update. I've been using Drush to my core updates, but it involves a lot more directory/file-moving (danger!). I use git, so if patches break, it's no biggie. Thanks!

I just used this upgrade and

I just used this upgrade and was just reminded how easy and straightforward it is.
Great work, dude, a lot of us can vouch that this is pretty important code you are working on :)

New patch

Hi, first of all, THANK YOU VERY MUCH for this one! It's so smooth!
A question for you: When the patch for drupal 6.19 to 6.20 will be released ?

Thanks in advance for your time


You provide a great service!!!

Thanks! And an update error

Hi there, thanks for providing these patches! This patch update method is definitely the easiest for me.

However, I had a bit of an issue with my 6.19 -> 6.20 upgrade. The dry run didn't give me any significant errors that I couldn't work around. So went ahead and applied the patch. However, the patch process got up to this point and failed:

patching file modules/user/user.module
patching file robots.txt
patching file sites/default/default.settings.php
patch: **** Can't remove file sites/default/default.settings.php : Permission denied

The problem is that it failed and stopped, leaving me with a half patched system. Fortunately the only remaining items were a few default theme folders, which I manually copied over to my root. But are there any workarounds so that this doesn't happen again?

Thanks a lot!

No write access to this file?

The message Permission denied does mean you do not have write access to the file sites/default/default.settings.php. Make sure, you either own it and it is writable by you or temporarily (and as the user who owns it) set it to writable by anyone before patching.

re: No write access to this file?

Thanks for the reply Bernhard.

Yes, this file was not writeable. I guess I was just wondering if there is any way to make the process a bit more failsafe, so that it continues patching the rest of the files even if there is an error.

re: No write access to this file?

I had the same problem with a single site configuration (where the settings.php is in sites/default and not in sites/example.com). I was wondering because with the --dry-run option I didn't get any error.

I guess, that the folder containing settings.php will be set to read only by the drupal installation script.

So you may run chmod u+w sites/default/ in drupal root before patching drupal and chmod u-w sites/default/ after patching.

A++ would patch again.

The standard upgrade instructions made me cry myself to sleep at night, but this patch file is absolutely amazing. I have my site running on a new core after only 10 minutes.

Thank you so much! :D

disable selinux first

If you use CentOS or Redhat with selinux, be sure to turn selinux either off or to permissive mode before patching.

Thanks for the patch,

Patch 6.x to 7.x?

Hi! I just patched Drupal to 6.20 and want to thank you - again! - for this great tool. I was wondering if you have any plans of releasing a patch for drupal 6.20 to 7.0? That would mean a lot to use who manage drupal on a daily basis. Thank you again.

Please try with caution

I created 2 patch files (see above):

  • drupal-5.23-to-6.22.patch
  • drupal-6.22-to-7.2.patch

When testing against the corresponding lower version it did look 100% good. Please try with caution anyway!

patch: **** strip count l is

patch: **** strip count l is not a number

Checked the hashtag, and it matches.

I'll be honest, I tried

I'll be honest, I tried patching while I was tired, this is really a no no. I've used quite a few of these patches before. The 6.22 to 7.4 took a wrong turn. I have a multisite install and I had all sites in off-line mode but I did neglect to set default themes. My default.settings.php file was unwriteable as well. Is there a logical way to resolve my issue ?

Currently I'm receiving the following errors:
Notice: Use of undefined constant DRUPAL_ROOT - assumed 'DRUPAL_ROOT' in /home1/.../public_html/includes/bootstrap.inc on line 1971

Warning: require_once(DRUPAL_ROOT../includes/errors.inc) [function.require-once]: failed to open stream: No such file or directory in /home1/.../public_html/includes/bootstrap.inc on line 1971

Fatal error: require_once() [function.require]: Failed opening required 'DRUPAL_ROOT../includes/errors.inc' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home1/.../public_html/includes/bootstrap.inc on line 1971

Try searching drupal.org

At my tests (vanilla 6.22 patched using drupal-6.22-to-7.4.patch) the default.settings.php is writable.

For the DRUPAL_ROOT problem try searching drupal.org, i.e. http://drupal.org/node/1009966. Looks like a 6.x -> 7.x upgrading issue.

I've been reading all that

I've been reading all that info and haven't been able to get a good handle on where to set the define("DRUPAL_ROOT", since I dont have an external script, would I make this change in the patch and run it again ?

Follow the standard upgrade path

I indeed pointed you to something not helpful for your situation, sorry! I guess something else is messed up in your setup. You rather should follow the standard upgrade path as described in drupal-7.4/UPGRADE.txt than using the patch file.

Malformed patch error when upgrading 7.0 to 7.2

You are doing an awesome job! I am using your patches all the time. Today was the first time when I got an error when doing a dry run.

When upgrading 7.0 to 7.2, I get this:

Patching file misc/watchdog-error.png using Plan A...
patch: **** malformed patch at line 6163: diff -Naur drupal-7.0/misc/watchdog-ok.png drupal-7.2/misc/watchdog-ok.png

Thanks in advance!

Got no error when throwing

Got no error when throwing the patch against a vanilla Drupal 7.0 as described above. Please make sure the patch file you downloaded does not changed somehow at your machine: check the MD5 hash using `md5` or `md5sum`.

I downloaded vanilla Drupal

I downloaded vanilla Drupal 7.0, extracted it and ran the patch against it with no problems. So something else was fishy with my install. My bad. Thank you!

Thank you very much. This is

Thank you very much. This is AWESOME!!! this way its also easy to maintain any core patches as i dont have to reapply them!

Thanks again for your great work

Thank you

Thank you for this amazing job!

upgrade from 6.20 to 6.22 for multisites

can i use the above described approach to upgrade my drupal multisites from drupl 6.20 to 6.22? if can't, how should i do this? thanks.

Patching Drupal will upgrade

Patching Drupal will upgrade all Sites in your sites/ directory. Make sure you run update.php for every site after upgrading.

Drupal 7.7 to 7.8

Any chance of getting a 7.7 to 7.8 update? I find that this method of updating drupal sites more convenient compared to their manual download upgrade.

Thanks - must have missed

Thanks - must have missed that release.