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 ]
related to child of duplicate of

Viewing Issue Simple Details
ID Category Type Reproducibility Date Submitted Last Update
0000692 [In-Portal CMS] Database bug report always 2010-04-10 07:25 2010-05-11 02:59
Reporter alex View Status public  
Assigned To alex
Priority normal Resolution fixed  
Status closed      
Summary 0000692: Translatable fields are not always created during table scan
Description Each field in unit config can have formatter class set. When formatter is set to "kMultiLanguage" class, then during table scanning (when adding new language or pressing "Rebuild Multilingual Fields" in "System Tools" section) missing translatable fields are created, so we have 1 field for each language, like "l<LANGUAGE_ID>_<FIELD_NAME>".

    * When "<FIELD_NAME>" is found in table, then it's parameters are used to create new translatable fields.
    * When "<FIELD_NAME>" is not found, then we create translatable fields based on information from field declaration in unit config.

There is an error in regular expression, that checks, that we already have given field created in table resulting field being reported as existing, but it doesn't in fact. For example when you have field "DestName" in table and you have translatable field "Name", then "DestName" is matched instead of "Name" and none translatable fields are added.
Additional Information

Web Development by Intechnic
In-Portal Open Source CMS
In-Portal Open Source CMS
Copyright © 2000 - 2009 MantisBT Group

Powered by Mantis Bugtracker