Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0011340 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] E. Translation | minor | always | 2009-11-12 16:42 | 2012-02-13 10:58 | |||
| Reporter | adrianromero | View Status | public | |||||
| Assigned To | alostale | |||||||
| Priority | urgent | Resolution | duplicate | Fixed in Version | ||||
| Status | closed | Fix in branch | pi | Fixed in SCM revision | ||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | 2.50MP8 | SCM revision | ||||||
| Review Assigned To | ||||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0011340: Centrally maintained fields are not translated depending on modules installation order | |||||||
| Description | Depending the order modules and translation modules are installed. Centrally maintained items of modules are translated or not. For example in a fresh installation we want to install the IDL module that contains windows with fields that are centrally maintained, The Spanish IDL translation module and the Spanish core translation module that contains the translation to Spanish of all the centrally maintained fields of the windows contained in the IDL module. If we install in this order: 1.- IDL Module 2.- Spanish core translation module 3.- Spanish IDL translation module Everything goes well and all fields of the IDL windows are translated. But if we follow the next installation order: 1.- Spanish core translation module 2.- IDL Module 3.- Spanish IDL translation module Then the IDL windows are translated but the centrally maintained fields. As a workaround, if we execute the process "Synchronize terminology" everything is fixed and centrally maintained items are translated. | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||||||
|
|||||||||||||||||
 Relationships |
|
Notes |
|
|
(0021782) adrianromero (manager) 2009-11-12 16:52 |
It seems that the "Synchronize terminology" process does not work as expected fixing the not translated fields. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-11-12 16:42 | adrianromero | New Issue | |
| 2009-11-12 16:42 | adrianromero | Assigned To | => alostale |
| 2009-11-12 16:52 | adrianromero | Note Added: 0021782 | |
| 2009-11-12 16:54 | adrianromero | Relationship added | related to 0011237 |
| 2010-01-05 12:36 | iciordia | Priority | normal => urgent |
| 2010-01-05 12:36 | iciordia | Status | new => acknowledged |
| 2010-01-05 12:36 | iciordia | Status | acknowledged => scheduled |
| 2010-01-05 12:36 | iciordia | fix_in_branch | => pi |
| 2012-02-13 10:58 | marvintm | Relationship added | duplicate of 0018383 |
| 2012-02-13 10:58 | marvintm | Status | scheduled => closed |
| 2012-02-13 10:58 | marvintm | Resolution | open => duplicate |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |