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
If a container (created by ext:container) is not named, the content is exported through the L10N Manager but the translated content is not imported. If the option "delete localizations before import" is not selected, no container in the target language is created. If the option "delete localizations before import" is selected, then a container is created (and set to hidden), but the content only says "(copy 1)" as the title and there are no elements created within the container.
If the "title" field for the container is filled out, then the export/import works properly.
The text was updated successfully, but these errors were encountered:
Update: We found that if the box "New/changed content only" is not checked when exporting the XML file, then the container is included in the export and is also created on the target language page when importing the translated XML file.
Note: This is only additional information. It does not fix our issue, as we have to have the "New/changed content only" box checked for our workflow to function properly.
If a container (created by ext:container) is not named, the content is exported through the L10N Manager but the translated content is not imported. If the option "delete localizations before import" is not selected, no container in the target language is created. If the option "delete localizations before import" is selected, then a container is created (and set to hidden), but the content only says "(copy 1)" as the title and there are no elements created within the container.
If the "title" field for the container is filled out, then the export/import works properly.
The text was updated successfully, but these errors were encountered: