You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now TAP has functionality for multilingual tours, I am trying to export a tour as a multilingual tour.
I create a tour node, translate this node in another language
I create stops, and create translations for that stops in the named tour
So far, that works fine.
But when doing an export as bundle or doing an export as xml, I don't get get correct stops. That means:
Stops are not labeled with their correct language (lang="nl")
Translated stops are not appearing, only the original stops
Two questions:
is translating individual stops the right way to create a tour in another language?
If so, is the code correct in requesting the correct translation of a node, and is the language for a tour correctly transfered to function that builds a stop?
The text was updated successfully, but these errors were encountered:
After investigating I see that the CMS only renders a node in one language, and not for all languages at once as in the specification of tourML.
I have succesfully patched the code that it renders all the titles at once, but have problems with including the sources for each language in an asset.
Now TAP has functionality for multilingual tours, I am trying to export a tour as a multilingual tour.
So far, that works fine.
But when doing an export as bundle or doing an export as xml, I don't get get correct stops. That means:
Two questions:
The text was updated successfully, but these errors were encountered: