Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
While testing the upgrade path on a couple of machines of mine (both Windows-equipped) I get the attached error.
The first one I tried the upgrade on has the following AMP stack on Windows XP:
Apache 2.2.17
MySQL 5.5.8
PHP 5.3.5
The second one has the following AMP stack on Windows 7:
- Apache 2.2.11
- MySQL 5.1.33
- PHP 5.2.9
Attached you can find the D6 test database I was using for the upgrade. I'll try to investingate when I have more time.
Comment | File | Size | Author |
---|---|---|---|
#3 | upgrade-1245980-3.patch | 519 bytes | plach |
drupal_6x.sql_.zip | 80.39 KB | plach | |
d6upgradewin.png | 16.46 KB | plach |
Comments
Comment #1
marcingy CreditAttribution: marcingy commentedI saw this this morning and having finally finished rebuilding my pc after a hard disk failure, I'll try and take a look at this issue over the next couple of days on an xampp stack.
Comment #2
plachAdditional detail: the OS running on the first machine is Windows XP SP3, while the second machine has Windows 7 Home Premium 32 bit SP1.
Comment #3
plachThe attached patch fixes the issue: it seems that, only on my Windows boxes (I tested the db attached in the OP on Linux and everything went well), the schema changes in
taxonomy_update_7001()
are not picked up and makeuser_update_7006()
(which btw triggers anentity_get_info()
call by callinguser_permission_get_modules()
!) fail.The reason why all of this happens only on Windows is beyond me. Would love if someone more into the update system could explain this.
Comment #4
marcingy CreditAttribution: marcingy commentedCan recreate on windows 7 64 bit xampp.
Comment #5
marcingy CreditAttribution: marcingy commentedHave appled patch in #3 and the update now completes.
I can't offer any insight to why this is but rtbc from me assuming the test is green.
Comment #6
marcingy CreditAttribution: marcingy commentedComment #7
catchThere's a critical, rtbc issue in the queue for user_update_7006(), please see if that fixes it.
Comment #8
plach@catch:
The patch in #1234834: 'module' column of role_permission table is not populated on upgrades fixes this, but I don't think it's the same issue: it just avoids it to happen. The problem I was able to track here is that on Windows the static cache of
drupal_get_schema()
holds different values than on Linux.Comment #9
chx CreditAttribution: chx commentedAvoiding it to happen is exactly what that issue is about. I bet a ton more issues are duplicate.
Comment #10
plachI'm only afraid this could come up in some other form elsewhere, since it might not be strictly related to the upgrade path.