Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello,
I am having this warning when editing custom content types:
user warning: Unknown column 'status' in 'field list' query: UPDATE locales_target SET status = 1 WHERE lid = 2590 in /htdocs/sites/all/modules/i18n/i18nstrings/i18nstrings.module on line 448.
Could anyone tell me what does that mean and how to solve it? I've performed a search in drupal.org but didn't find any information.
Thank you very much
Comments
Comment #1
Rar9 CreditAttribution: Rar9 commentedGot the same Problem... any hint what to do your that?
user warning: Unknown column 'status' in 'field list' query: UPDATE locales_target SET status = 1 WHERE lid = 2850 in httpdocs/sites/all/modules/i18n/i18nstrings/i18nstrings.module on line 448.
the lid goes from 2850 to 2853 :-)
By what I notice that taxonomies aren´t synced correctly anymore
Comment #2
wuh CreditAttribution: wuh commented* This is a poor issue title - can someone please update it to something more relevant?
Problem:
On updating i18n strings using the Translate Interface tool, the following warning is displayed twice:
user warning: Unknown column 'status' in 'field list' query: UPDATE locales_target SET status = 0 WHERE lid = 1986 AND language = 'fi' in /home/wuh/public_html/ecobohemia.rootsydev.co.uk/sites/all/modules/i18n/i18nstrings/i18nstrings.module on line 216.
This does not seem to affect the usability of the module, but it could be having an adverse effect somewhere that I haven't spotted.
Comment #3
pluess CreditAttribution: pluess commentedSame here.
It tries to update a column in the table . But this column does not exist.
Comment #4
j0nathan CreditAttribution: j0nathan commentedSame warning message with different lid when running update.php.
Comment #5
jim005 CreditAttribution: jim005 commentedsame problem for me ! any solution ?
Comment #6
c-c-m CreditAttribution: c-c-m commentedIs there something that can be done to solve this behaviour? I have not found any pattern to reproduce: this warning still appears randomly (at least for me), mostly when I edit content.
Comment #7
Vote_Sizing_Steve CreditAttribution: Vote_Sizing_Steve commentedSubscribing.
Comment #8
Vote_Sizing_Steve CreditAttribution: Vote_Sizing_Steve commentedI successfully ran
ALTER TABLE locales_target CHANGE `status` `i18n_status` INT NOT NULL DEFAULT 0
in my navicat sql - perhaps the brackets part of the broken update.php'sALTER TABLE {locales_target} CHANGE `status` `i18n_status` INT NOT NULL DEFAULT 0
are causing the error?Comment #9
jasom CreditAttribution: jasom commentedI just update i18n from 6.x-1.7 to 6.x-1.9 and have this message after update.php script was done:
Comment #10
castawaybcn CreditAttribution: castawaybcn commentedSame error, does not seem to have any other side effects, but I am not entirely sure.
Comment #11
diond CreditAttribution: diond commentedThis issue also affected my fresh install of 7.x i18n module in D7. There's a chance it may affect the updating of certain strings on the site. Try changing the display name of one of your Content Types and see if you are successful. This field that is missing in the {locales_target} table is responsible for telling the i18n & i18n_status modules as to what translations need updating (nice feature to have).
BTW the brackets {} around the table name are supposed to be there and a good feature. Those brackets allow Drupal to automatically affix any "DB table prefixes" that may be used on a site.
SOLUTION: I just went into my PHPMyAdmin, opened the {locales_target} table, and manually added the missing DB field (Added an INT field with Default value 0, NOT NULL, and 11 long). All my translations and updates have worked since ;) Hope this helps.
Comment #12
Pascal.s CreditAttribution: Pascal.s commentedI had the same problem after updating i18n module to the last version in D6. I went to my database, select all tables and "repare table". Seems to have fix the problem for me so far!
Comment #13
joseph.olstad