In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Dependency Graph

[ View Issue ] [ Relation Graph ] [ Vertical ]

Viewing Issue Simple Details
ID	Category	Type	Reproducibility	Date Submitted	Last Update
0001270	[In-Portal CMS] Localization	bug report	always	2012-05-05 10:02	2012-07-25 05:30

Reporter	alex	View Status	public
Assigned To	alex
Priority	normal	Resolution	fixed
Status	closed

Summary	0001270: Multiple language import fails
Description	Problem #1: If you have 1 language and you import language pack, that has 5 new languages, then it will fail with SQL error, that no l6_Translation column exists. This happens, because there are only columns for first 5 languages after clean In-Portal installation. I think, that after new record is created in Languages database table we should also create corresponding new columns in all database tables, that have translatable fields in them. Not sure if this happens already (maybe after language import was finished) or after each new language is created (as I would like it to work). It seems, that problem was there right after we changed how phrases/e-mail events are stored in 5.1.0. Problem #2: If you have language pack that has 1 language with not translated phrase and 2 languages where this phrase is translated then you'll get "Column count doesn't match value count" sql error during import. Problem #3: <?xml version="1.0" encoding="utf-8"?> is not being added to language pack.
Additional Information