RWS Support

Language Weaver Planned Maintenance Activity

We will be undertaking maintenance for Language Weaver on Saturday September 23rd, 2023, between 06:00 AM UTC and 08:00 AM UTC. This planned maintenance is exceptional and is being carried out to enhance the performance of our platform. During this time, you will not be able to log in to the Language Weaver Portal or use the API.

Should you have any queries, please contact RWS Customer Support or reach out to your Account Manager.
We apologize for any inconvenience this may cause.

RWS Support

Latest Articles

For Tridion Sites 9.6, can AWS CD Docker containers use ARM based processors instead of x86 based processors? 9/21/2023 11:33 PM

Copy/Move Templates from PROD to DEV The customer had performed a DB refreshed updating data from PROD to DEV but the template names did not make it through. A manual copy paste of the same resolved the issue. 9/21/2023 9:39 PM

WorldServer - in the Modern User Interface, "Change Attributes" displays only the selected project attributes from the Project Type instead of displaying all available project attributes By enabling the option Attribute Availability to the Project Type template, where you can select Show all Attributes when changing their values, all project attributes will be visible when selecting Change Attributes in the modern User Interface for projects created with this Project Type. This applies also retroactively: as soon as you activate this option and save the change in the Project Type, you will be able to view ALL project attributes in the Change Attributes window even if the projects were created before the change. Note: the option is deselected per default. 9/21/2023 7:43 PM

Tridion Sites Product Release Policy 9/21/2023 4:55 PM

How to prepare project that has the Language Weaver Edge as a translation provider so that the translators don't get the "Sufficient permissions for opening the translation provider could not be obtained" error message in Trados Studio? We are prepping projects at Trados Studio’s level prior to publishing them on GroupShare. We do have Language Weaver Edge installed as an on-premise translation provider. Each of our user has a distinct API key to authenticate with LW Edge. How do we prep projects so that LW Edge is set as a translation provider but also allow translators to authenticate with LW Edge using their unique API key? 9/21/2023 4:07 PM