I have a great problem when I try to use i18n in Drupal 5.2.
There were couples of errors. And the primary link on top of the page was disappear.
It said that I should run update.php and update i18n module.
There were couples of errors again.
After that my site went down I was redirected to node with en/ in front of and found nothing (404).
I went back to the frontpage.
My Navigation and admin page items were doubled!
I disabled the i18n module and run update.php again and cannot fix this problem.

How to fix this?

Unknown column 'm.language' in 'where clause' query: SELECT m.mid, m.* FROM menu m WHERE (m.language ='en' OR m.language ='' OR m.language IS NULL) ORDER BY m.mid ASC in /var/www/html/eic/includes/database.mysql.inc on line 172.

Comments

hedac’s picture

hedac commented

I had the same problem trying to upgrade from 4.7 to 5.3....
and now I don't know how to put my menus and administration pages back to normal.... some elements of administration menus are missing... and the ones that are there are doubled.... and all the menus are doubled.

hedac’s picture

hedac commented

I tried again with the dev version 2007-Nov-04
and it works ok now... :)

I notice one difference... in the administration menu.. it says i18n. and no description.... and before it was Multilingual system...

jmlavarenne’s picture

jmlavarenne commented

I'm having the same issue (http://drupal.org/node/262904) with version 2.3

It seems like something that should be happening when update.php is run is not taking place, like the table field getting created.

I saw a similar issue with Views module - maybe we need to force a specific update# for things to run properly?

There is no language field in the 4.7 install in the menu table, and after running update no language field appears there for the 5.7 install.

jmlavarenne’s picture

jmlavarenne commented

I'm also seeing a problem with the sequences table - I guess I should file another issue...

Is it possible that on install the module fires-up a hook or calls on of it's functions before the menu table gets altered?

I seem to have fixed the issue for myself by manually running the offending update in my SQL client previous to enabling the module

ALTER TABLE {menu} ADD language VARCHAR(12) NOT NULL default ''

So far so good...

jose reyero’s picture

jose reyero commented
Status: Active » Closed (won't fix)

Consider upgrading to 6.x