The xmlControlField.js file that is used to load the value_builder xml files for fields 006 and 008 always uses the file in the "en" directory, ignoring the current language.
This prevents translations in those xml files to work, because the "en" file is always used :
Created attachment 4986 [details] [review]
Fix xmlControlfield.js so the xml files are fetched in the correct language directory.
Please note that the xml files still can't be translated by the "translate" script. (See Bug 6709)
To test this patch, you'll have to manually modify the xml files of a language other than "en".
Also note that the xml file might still be in your browser cache. Remember to empty your browser cache when testing this patch.
Created attachment 4998 [details] [review]
[SIGNED-OFF] Bug 6715 - Fix xmlControlfield.js so the xml files are fetched in the correct language directory.
xmlControlfield.js was always fetching the "en" xml file, preventing the translations
Signed-off-by: Katrin Fischer <Katrin.Fischer.email@example.com>
- Apply patch
- Install language files, example: perl translate install de-DE
- Edit .xml files for value builders 006 and 008
- Test by creating a new record and using value builders
Easy patch to read, adds valuable information to templates, marking as Passed QA
Pushed, please test
The fix for this bug was published in the 3.4.5 release. If you were the reporter of this bug, please take time to verify the fix and update the status of this bug report accordingly. If the bug is fixed to your satisfaction, please close this report.
There have been no further reports of problems so I am marking this bug resolved.