Translating instances has always been of importance. After all, what good is working on an instance where you have to google the translation of every fourth word. Translated text fields allow the same field to display different content based on the user's language. Some changes have been made to the ability to translate text in order to accommodate different dialects.
We have recently moved the Title field on the Catalog Category (sc_category.title) table to be a part of the Translated Text type, instead of Translated Field type. This is because Translated Text type fields allow for multiple translations to be entered into sys_translated_text table, while Translated Field was only supporting single translation.
The drawback is that, when upgrading older versions to Eureka, it may happen that your update sets will not track the Title field anymore. Translated Text fields were previously reserved for Items that are considered data, and as such, not tracked by the Update Set.
This effectively means that you can end up with:
- Updates that are not captured at all
- Update captured and transferred as for default language instead translation. In this case, translated title (e.g. German) replaces you default title (e.g. English) for all languages.
This does not happen on out-of-the-box instances on Eureka and upgrading to Fuji will apply the following fix.
In order to make Title field on Catalog Category table tracked by the Update Sets, specific serialiser needs to be used and that is achieved by adding new dictionary attribute to that field which would force use of the TranslatedTextXMLSerializer on it
Make the Title field on Catalog Category table tracked by the Update Sets by adding the Dictionary tribute: serializer=com.glide.script.TranslatedTextXMLSerializer
2 Comments
