D52 -> D6 upgrade: missing columns in i18n_strings table
eigentor - March 9, 2009 - 02:34
| Project: | Internationalization |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
I must be severely missing something. I am trying to upgrade from 5.2.5 to 6.1.0. But this cannot work, due to the table i18n_locale_strings. This is renamed from i18n_strings to i18n_locale_strings in 5.2.5 "For a smooth D6 upgrade".
But 6.1.0 tries to change a table i18n_strings, which now no longer exists. It also tries to change a column name objectid to oid, but the column objectid also does not exist.
There must be a database upgrade missing - but where? Like this it is completely impossible to upgrade.
#1
The same problem here...
I would very much appreciate a bug fix or a temporary solution.
#2
There are two bugs :-(.
1. The first one is in D52 and looks like a copy and paste bug or typo (flipped table names).
2. The second is that the D6 version does not add the 'oid' column on update.
I've committed both fixes to D5 and D6, so you may try to use the next D5-DEV to prepare your D5 for the upgrade and then move to D6.
D5: http://drupal.org/cvs?commit=250824
D6: http://drupal.org/cvs?commit=250826
Please report back if this fixes solve your issues! I wasn't able to test this myself, but code wise it need to be correct.
#3
Ahm, will be fixed in 6.x-1.2 :-)
#4
It looks like this needs more work... it looks not ready to me... there are more columns missing and I do not have an idea how the upgrade path is... I've only added the missing columns in 6004, but this hook is currently disabled.
#5
#6
#7
@Jose: Can you explain what we need to do for updating the data in the table to the new D6 schema?
#8
#9
It looks like quite a few sites were upgraded through the broken path. Could the maintainers of this module please write up some instructions about how to fix the broken D6 database schema? Many thanks.
#10
From an email from jose I believe there are no plans to upgrade experimental modules... This was no decission, but my impression. Maybe someone like to work on it otherwise it may never done.
#11
Well, there's a reason that module was marked as experimental, anyway, here's what happens:
The last 5.x update just moves the table out of the way so we can do a clean start with with 6.x version while still preserving your data.
Then there was this i18nstrings_update_5900() that was commented out in the module...
Now I hope it will update, though your old strings (5.x) won't be updated but they won't be lost either (they'll be in that i18n_locale_strings table waiting for someone to write some queries to recover them).
#12
Marked #633022: Upgrade problem from 5.x-2.5 to 6.x-1.2 as duplicate.