Topic > Taxonomy Not working in portal

[Community Alums]

We created the Topic name of the new Taxonomy we have created in the sys_translated_text table, however the text is not convereted to that langauage.

[Community Alums]

HI @Vamsi Paidi ,

The new sys_translated_text record is generated once you save and publish the topic.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Alex Coope - SN]

@Vamsi Paidi,

If you've created the translations in the correct way, then in order to see the translations you will need to fully log out of the instance and log back in in that translated language. This is because the browser will have cache'd the strings in English. I'm afraid a cache.do won't make a difference here and only a full log out and login in the other language will work,

Many thanks,
kind regards 

[michaelward]

I did have the same issue it seemed.

However, I double checked the sys_translated_text table, made sure I created a record with the proper document / sys_id reference of the topic and translated text and language.  This did work and the topic finally showed on the mega menu in translated text.

I did notice though that none of my custom taxonomy topics were translated upon installing the language translation plugins.  Only the OOTB demo data translations were performed.  The only difference I think could be the scope as my custom topics were not in the Employee Experience taxonomy scope.  I also noticed I seem to be missing a number of the localization framework artifact configurations for EC content tables.  I expect the missing artifact configurations is why automatic translation is not performed, and furthermore, I do not see an associated LF processor script include for taxonomy topics. 

Overall, at the least for me, the manual created record in sys_translated_text did result in the translated topic appearing in the mega menu upon switching languages.

[Alex Coope - SN]

@michaelward,

So the Language Packs will only contain what is ootb (as they are our translations from the base product, meaning that you would always need to add translations for anything you build in the platform). 

Not sure if you've seen my blog post on how to translate a Portal, but my prototype Portal artifact (for the Localization Framework) will pick up the taxonomy,

Many thanks,
kind regards