Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Currently, only 6.x-2.x can be upgraded to 7.x-1.x but as the latter will become stable before 6.x-2.x, We want to provide a way to upgrade from 6.x-1.x.
Working on a patch.
This is imho the last beta blocker.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | upgrade_from_1_3.patch | 11.74 KB | berdir |
| #4 | upgrade_from_1_2.patch | 9.9 KB | berdir |
| #1 | upgrade_from_1.patch | 11.22 KB | berdir |
Comments
Comment #1
berdirOk, tested the patch by upgrading from 6.x-1.x and 6.x-2.x, both works flawless.
Please test!
Comment #2
naheemsays commentedsubscribing - I will test this in a bit.
Comment #3
naheemsays commentedThe patch does not apply cleanly - two parts of it not are rejected, but after recent patched, they seem to be not needed?
I tested the basic functionality and it works after upgrade now.
Comment #4
berdirYep, the patch contained some unecessary things.
Updated, this should be clean now.
Any chance for another test from anyone else during the next few days? This is the last thing that is blocking 7.x-1.x-beta1...
Comment #5
berdirOk, some improvements...
- Added hook_update_last_removed(), only updating from 6.x-1.3 or later is supported, this is the version that updated all the indexes in 6007. Note that there is currently a bug so the warning is now shown, see #834848: Warning message regarding hook_update_last_removed() is not displayed.
- Incorporated the index changes from #820238: Improve indexes on pm_* tables and updates the correct indexes now in privatemsg_update_7003. This is something that is currently broken in 6.x-2.x too.
Can you please test the upgrade again with this patch (All you need to do is restore all pm_ tables you surely have backuped and set schema_version of privatemsg to 6007 (try 6006 or anything lower to test hook_update_last_removed, see issue linked above) and privatemsg_filter to 6003 in the {system} table.
Comment #6
BenK commentedI tested the latest patch and everything is working great. Patch applies cleanly now and upgrade occurred without a hitch. All functionality after the upgrade seems to be working well.
Also, I should mention that I just went ahead and did a full upgrade of a Drupal 6.20 site to test. I made a bunch of messages before the upgrade (using the PM 6.x-1.x branch), upgraded the site to Drupal 7, and then upgraded PM to the 7.x-1.x branch). Everything went smoothly.
So congrats... this is RTBC!
--Ben
Comment #7
berdirGreat, thanks, commited.