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

View Revisions: Issue #41751 All Revisions ] Back to Issue ]
Summary 0041751: Problems to translate selector fields 'centrally maintained'
Revision 2019-09-17 17:22 by caristu
Description Translations for selector fields defined as 'centrally maintained' should be retrieved from the ad_element of their related ad_element.

Therefore, there exists triggers that detect changes done in the ad_element/ad_element_trl tables in order to properly update the labels of different application elements like parameters, selectors etc.

In the case of selector fields, this trigger is the OBUISEL_ELEMENT_TRL_TRG but it currently is not working properly.
Revision 2019-09-05 09:23 by caristu
Description The TranslationManager just exports to the translation XML files the selector fields which are not flagged as centrally maintained[1]. This seems to be done because centrally maintained fields should take its translation from their related AD_ELEMENT.

But this is not being taken into account when generating the selector view, because the translation are being searched just in the corresponding _trl table[2].

[1] https://code.openbravo.com/erp/devel/pi/file/tip/src/org/openbravo/erpCommon/ad_forms/TranslationManager.java#l457 [^]

[2] https://code.openbravo.com/erp/devel/pi/file/tip/modules/org.openbravo.userinterface.selector/src/org/openbravo/userinterface/selector/SelectorComponent.java#l698 [^]
Revision 2019-09-04 17:28 by caristu
Description The selector fields 'centrally maintained' should not need a record in the correspondedt _trl table.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker