Posted by aiphes on February 15, 2012 at 10:56am
3 followers
Jump to:
| Project: | Localization update |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi
i would use this module with D6.24 but seem to be an issue with new drupal update..;this is an example that i take :
Unknown column 'l10n_status' in 'field list' query: INSERT INTO d6mg_locales_target (lid, language, translation, plid, plural, l10n_status) VALUES (5782, 'fr', 'Ce décompte peut être erroné dans la mesure où certains fichiers n\'ont pas besoin d\'être renommés.', 0, 0, 0) in /var/www/drupal6/sites/all/modules/l10n_update/l10n_update.locale.inc on line 369.
it's on a fresh install,on others (multisite) all look good..
thanks
Comments
#1
I've tested the installation of the module on Drupal 6.24. The l10n_status column is created as it should. Data is entered into the field without any problem. I do not use table prefixes.
Did you receive any error messages when installing the module? l10n_update adds the 'l10n_status' field when it is installed. Do you use the latest dev release?
#2
seem i use the 6.x-1.0-beta1+17-dev so do i change for dev version ?
#3
This is an Localization Update issue, so I am talking about versions of this module.
#4
i talk about the same module and in drush and on /admin/build/modules the module version for l10n_update is 6.x-1.0-beta1+17-dev ...look strange for me too..for test removed the actual module folder and replace it by the fresh dev version, and all works as designed ! updates did put the mess in module folder i think, drush still display the wrong version after cron, clear cache and update db..
#5
info ; on fresh install with dev version i've this : Localization update 6.x-1.0-beta1+17-dev (2012-Jan-26) perhaps an error in dev code..? an update to 2012/02/22 is avaible but not yet done
#6
I now see that the packaging script adds dev version numbers like '6.x-1.0-beta1+17-dev' or '6.x-1.0-beta2+1-dev'.
Use the latest dev. Your problem was fixed in #1449376: l10n_update_cache are not in schema array on install hook.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.