Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0014551
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajorhave not tried2010-09-14 18:112010-10-01 00:00
ReporternetworkbView Statuspublic 
Assigned Toalostale 
PriorityurgentResolutionno change requiredFixed in Version2.50MP22
StatusclosedFix in branchpiFixed in SCM revision
ProjectionnoneETAnoneTarget Version2.50MP23
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version2.50MP21SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0014551: When a translation module is installed the synchronize terminology is not executed

DescriptionWhen a translation module is installed the synchronize terminology is not executed.
This is a problem with fields checked as central mantained because the fields are not translated with the translation of the module.
Steps To Reproduce-Create a translation module that translate another module where there are fields defined as central mantenaice
-Install the module in an application where the module to be translated is installed.
-After recompile access to the application and see that the fields checked as central maintenance are not translated.
Proposed Solution-After install a translation module execute the process ad_syncronize

TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 00146892.50MP22 closedalostale Translation: If you apply any translation module on top of MP21 some fields get not translated 

-  Notes
(0031492)
alostale (manager)
2010-09-30 11:21

Translation process shouldn't run synchronize terminology as this process is a development tool which only affects to modules set as in development.

Translation process relies on *trl triggers to populate centrally maintained fields based on their elements.

Is in this point where an issue was detected in mp21 (0014689), could this issue be a duplicate of that one? If not, could you provide a sample obx to reproduce it?


(0031516)
networkb (developer)
2010-09-30 13:59

This bug can be closed. The problem was related with the bug 0014689, that has been solved and publised on 2.50mp22 release.
Thanks.

- Issue History
Date Modified Username Field Change
2010-09-14 18:11 networkb New Issue
2010-09-14 18:11 networkb Assigned To => alostale
2010-09-20 08:56 alostale Target Version 2.50MP22 => 2.50MP23
2010-09-20 08:56 alostale Status new => scheduled
2010-09-20 08:56 alostale fix_in_branch => pi
2010-09-30 11:18 alostale Relationship added related to 0014689
2010-09-30 11:21 alostale Note Added: 0031492
2010-09-30 11:21 alostale Status scheduled => feedback
2010-09-30 13:59 networkb Note Added: 0031516
2010-09-30 14:00 networkb Status feedback => closed
2010-09-30 14:00 networkb Resolution open => no change required
2010-09-30 14:00 networkb Fixed in Version => 2.50MP22
2010-10-01 00:00 anonymous sf_bug_id 0 => 3079038


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker