Known issues in Translation Manager

The following list describes issues that are known to exist in Translation Manager.

Configuration path isn't displayed in Source/Target items
Problem: When you have configured an item so that it can be a Target for translations or a Source for translations, when you create a Translation Job, after you have selected whether to translate To (pull job) or From (push job) in the Translation Job Details the Configuration path is not displayed.
Solution: The problem is a display issue and does not affect the actual sending of content.
Translation Jobs list is not displayed if SDL TMS or SDL WorldServer configuration is incorrect
Problem: The Translation Jobs list is not displayed, and an error is displayed, if the SDL TMS or SDL WorldServer URL configuration is incorrect.
Solution: Fix the URL in the TranslationManager.xml file.
Authorization Required column is present when SDL WorldServer is configured
Problem: If SDL WorldServer is configured, the Authorization Required column should not be visible in the user interface for Translation source configuration and Translation target configuration sections.
Solution: If SDL WorldServer is configured, ignore the setting as it is only relevant for SDL TMS only.
A Javascript error is thrown in IE 9 when sorting on To-From
Problem: In Internet Explorer 9, when you add an item to an existing job, in the dialog that opens a Javascript error is thrown when you try to sort entries by clicking the From/to column.
Due date set incorrectly in older versions of SDL TMS
Problem: In SDL TMS versions 2007 SP4 to 2011, the due date of a translation job is always set to the creation date of the job plus 1 week, regardless of what the required date was sent in the job request.
Refresh browser cache after installation
Problem: After you have installed Translation Manager, the Translation Manager functionality does not appear in the Content Manager Explorer interface.

Solution: Refresh your browser cache to view the changes in the Content Manager Explorer.

Check-in failure due to Schema violation
Problem: When translated content obtained from SDL TMS fails to validate against the Tridion Schema, for example due to schema violations of restricted fields or if someone changed the schema since the content was sent, the translated content will not be applied to the Tridion item (check-in will not be performed) and the job will enter the Error retrieval state in the Content Manager and in the Translated Content Retrieval state on SDL TMS until the problem is corrected.
Solution: To prevent check-in failure due to schema violations of restricted fields, it is recommended to:
  • Create an analysis (ANL) file to exclude translations of fields with restricted values
  • If you want to translate a restricted value field, define a workflow step on SDL TMS after the translation step to verify that the translation is valid, for example a simple value validation or validating the XML against a Schema.
LDAP users displayed without Directory Service name

Problem: If you have configured the Content Manager so that it can access LDAP directories, you can add users from an LDAP compliant directory service. LDAP users are displayed in the Content Manager with Directory Service name. However, in the Info tab of a Translation Job dialog, a user from an LDAP directory is displayed without with the Directory Service name.

Save Translation Job possible despite no mandatory Business Unit specified

Problem: When you specifying mandatory Business Units in the Translation Manager configuration file, existing Translation Jobs in the In Definition state do not have a value applied. When you open the Translation Jobs but do not specify a Business Unit, you can still save the Translation Job.

Selecting 400+ Components for translation causes GUI error

Problem: When selecting more than 400 Components (or any other items) for translation, the Translate Job dialog appears as a blank screen.

Solution: Create smaller Translation Jobs, or send Folders.

Error Sending reports only one error

Problem: When there are two or more items that fail when sending to translation (Error Sending), an error message is displayed for only one of them.

Solution: Fix the error and choose Retry Sending.