We want to send components, pages for translation to world server, from 060 canada publication. but if components, pages are not localized or locally created then translation option is missing. though translation option is enabled for all parent publications. enter image description here

when we started reviewing the settings of all parent publications we have found that we have set different project types [setup at world server] in parent and child which is part of the requirement.

For testing purpose we found that if we use same project type [setup at world server] and client [setup at world server] for all publications then translation option is available for all items inherited from parent.

to summarize our requirement:

  1. we want to use 2 project types [setup at world server] depending on target language.

  2. if possible we also want to use 2 client [setup at world server].

I have attached existing translation settings on each publication level. Following is current publication properties in terms of translation tab.

enter image description here

  • The configuration of WorldServer project type and client have to match to create the language "pairs" from Source to Target in Tridion Publications. Jun 2, 2020 at 12:43

1 Answer 1


For the translation source and target Publications to properly match, they must have matching configuration (same Project Type and Clients for WorldServer).

See the Translation Manager resolving logic, and specifically how push and pull translations work.

Note that a SDL WorldServer configuration specifies the Client and Project Type that specifies the source language. Also, "If no Parent item is configured, an item cannot be sent for translation."

Be sure you've set up your Source(s) and Target(s) (and any combination Source-Targets) as well.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.