Closed (fixed)
Project:
Localization server
Version:
5.x-1.0-alpha2
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Dec 2007 at 12:17 UTC
Updated:
2 Jan 2008 at 22:53 UTC
Jump to comment: Most recent file
Comments
Comment #1
hass commentedOps, this problem occurred when i'm trying to import an already translated pot file into one project...
Comment #2
hass commentedThis modules are active:
0. Locale
1. Localization community
2. Localization community for local packages
3. Translation template extractor
4. Upload
+ standard core
Comment #3
hass commentedLooks like caused by line 789 in l10n_community.module. The query does not contain all required columns.
Comment #4
hass commentedThis fixed the first time import without suggestion check box for me, but i'm totally unsure if this defaults are all correct. Additional to this the above INSERTS in
if ($suggestion) {are broken, too.Comment #5
gábor hojtsyYou run on a MySQL in strict mode apparently, as otherwise these are silently ignored. Hm, anyway, added defaults in this patch. Please test with this applied and the update run. Patch is against alpha2.
Comment #6
hass commentedParse error: syntax error, unexpected '}' in C:\Inetpub\wwwroot\drupal5localize\sites\all\modules\l10n_server\l10n_community\l10n_community.install on line 158
Comment #7
gábor hojtsyOh, please add that missing { on the foreach and test again.
Comment #8
hass commentedfixed patch
Comment #9
gábor hojtsyDoh, it is a bit late. I should have used db_change_column() actually.
Comment #10
hass commentedI tried an import, reimport and editing of some translation strings it looks now working as expected. thx
Comment #11
gábor hojtsyGreat. We still need to make this use db_change_field() for the APIs sake :) One less item to care if someone likes to make the module work nicely with postgresql.
Comment #12
hass commentedSorry, but db_change_field is D6 only... now we have D5... so the patch is ok.
Comment #13
gábor hojtsyHm, I understand that this ALTER approach does not work with postgres, but we don't have postgres users so far, and they will get the new schema anyway, so this will not affect them. That said, to concentrate on more important tasks, I committed this. Thanks!
Comment #14
gábor hojtsy