Despite the translation system you select in the installer, you can still configure different translation systems in a single Tridion CM, but it will be a single translation system per Blueprint hierarchy.
For instance in the picture below, 200 Content EN is an English source publication configured to use Language Cloud for any of its child publications ...
It is unfortunately "just the way it works".
You can file an enhancement request (which would obviously not do anything for the existing versions).
You can hook into the Tridion save event (TM identifies itself in the session, so you would know it's not a user saving). In this save event it is possible to read the old data and move over the fields that ...
Any third parties will have the potential to benefit from Translation Manager improvements (e.g. ability to send minor versions within workflow), but like Nuno pointed out Translation Review is only available with TMS and WorldServer.
At least compared to others CMS's, things unique to SDL's connector include:
Better batch handling of translation jobs and ...
We wondered something similar some time ago. From memory... it's submitted as a single job/transaction from the Tridion/TMS perspective and within 2013 there's no concept of retrieving 'bits' of the job.
Although this single TMS job/transaction may then split into several different workflow processes (depends on the Translation Service you're using) Tridion ...
The url change that you described in the beginning has nothing to do with with this problem.
This is bug in TM 8.1.1
It happens when you have workflow step in World Server workflow that has 3-4 letter word in name of workflow step (e.g "Set Asset Translation Status").
There is hotfix for that TM_184.108.40.20675
Ask support for hotfix.
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 ...
Unless you have any restrictions on the number of Publications that you can have in your Tridion license, then I would definitely go for Option 1.
The main advantages of this are:
Levels 020, 030 and 040 will just contain content (i.e. Components, Folders and Categories/Keywords. Whereas level 070 will also contain the structure of your site (i.e. Pages ...
SDL Language Cloud is enabled by default. So in installer you can just select World Server and you will get both.
If you already installed and want to add World Server to TM - see documentation
It is indeed beter to separate different translation systems in different publications. See previous answer.
1) No. There is not a one to one relation between a job in Tridion and a job in your TMS (translation management system in general, not SDL TMS specifically).
A job in the TMS will always belong to a single job in Tridion, but one job in Tridion can have multiple jobs in the TMS.
The split is done if the job gets too big, or it can happen if not all files ...
Indeed, your question might get flagged as off topic here.
If fast, "run time" translation is required then you will clearly not be able to rely on human translation due to the time that takes but instead will require some form of machine translation.
SDL Language Cloud has a machine translation API available that you could use (this is the technology that ...
A 503 response indicates that the service is temporarily unavailable. So it may be overloaded at the times when it gives this message, but working correctly when you manually check the URL. I'd suggest you look into the server logs of the service which is returning the 503 status.
It appears your login to TM or WorlsServer is not working. There are logs I believe in the TM client folder on the server.
Also, I have had an issue before where WorldServer was setup with https and I needed a hot fix. However, that was using an older version of the connector and I assume it's better now.
Basically there are three things that can fail (well, I am sure a computer somewhere can come up with number four that I didn't think about):
1) The plugin is not loaded
This is easy to verify - set the log to verbose and restart the TM service. In the log file should now contain an entry that will be either (assuming English logging)
Loading plugin with ...
Translation an item requires it to be localized. SDL Tridion 2013-SP1 does not support localizing an item before it has reached V1.
A common workaround is to create a workflow that check if it is a new item in the first step. If it is, it completes the workflow (creating a v1) and starts the workflow once more.
SDL Web 8 supports localizing items (and ...
It indeed looks like Worldserver side, please verify whether the "test" Client exists in WorldServer (Management -> User setup -> Clients). The message indicates that the Client has been deleted.
Is this for an old Translation Job created before the upgrade?
In theory changes in TranslationManager.xml should be applied immediately without restarting anything.
If you do not trust this and want to ensure new configuration is loaded - restart "Translation Manager" service and "Content Manager Service Host" service
For changes in WorldServer - things are cached for 10 min. And should eventually ...
I'm not quite sure if you've got a configuration problem, or if you're just not sure where to go next to continue the setup. One thing I'll point out is that if you're upgrading from WS 10 to 11, the API endpoint has changed (per the documentation).
Previously for WS 10, the endpoint was structured like:
<WorldServer username="admin" password="wsadmin"&...
The error indicates a network issue - I suspect this more so as you state
sometimes the bundle with 200 components is getting delivered
Can you check the event system logs?
Have you set the Translation Logs to debug also? - Perhaps there's something in here given the service polls the World Server service - is it often reporting issues in the ...
The translations.com extension provides the following features
Compatibility with all versions of Tridion from 2011 till Web8
Support for translation of Structure Groups, Pages, Components, Multimedia Components, Categories and Keywords and Bundles
Ability to customize notifications and integrate with workflows
Built-in change management, to be able to send ...
From your stack trace:
Object reference not set to an instance of an object.
at Translation.PlugIns.ResumeActivityUponTranslation.OnStateChanged(Object sender, TranslationJobStateChangeEventArgs e)
at Tridion.TranslationManager.DomainModel.TranslationJob.ChangeState(TranslationJobState newValue, Boolean validateStateChange)
To answer a part of your question - Yes, one Tridion translation job related to one TMS project and that itself go through some defined steps in TMS. There may be a separate workflow in TMS as well. Further, in SDL Web 8, the Workflow has been improved such that you may during a Workflow process send item for translation, which during the Translation System ...