In preparation for an upcoming customer meeting I have to configure WCM multi-lingual solution (MLS). The server is installed with v18.104.22.168 and CTC 4, and my objective is to enable multi-lingual support on the CTC demo site as this will make a useful demo platform for future engagements. Starting with v22.214.171.124 the Multi-lingual asset is bundled with WCM, and you just have to enable it. The first challenge was to locate documentation, which is not within the main portal wiki but under supplementary documentation, here.
I followed the installation documentation pretty closely, with the following steps:
- Ran the ConfigEngine tasks to deploy and install the PAA containing the multi-lingual components
- Used the installed library clone portlet to create a clone of the CTC Demo library, which I called CTC Demo DE for German locale content.
- Created a simple initial MLS configuration
- Created the Locale Owners group
- Ran memberfixer over the MLConfiguration_v7 library
- Created a configuration document in the library using the LocalizedConfigurationFileAT template
- Set up the document with the names of my libraries – CTC Demo (which already existed from the CTC install) and CTC Demo DE
- Under “General Settings” I configured authoringUIURL and storeOriginalWorkflow=true
- Under “Translation Table Settings” and “Localize Workflow Synchronization Settings” I took the defaults
- I didn’t set up any workflow so “SyncPublish Workflow Synchronization Settings”, “SyncExpire Workflow Synchronization Settings” and “SyncDelete Workflow Synchronization Settings” all took the defaults
Next week I need to look at setting up workflow so I’ll revisit the workflow configuration in a subsequent post.
Without doing anything else, the “Multi-lingual Solution” section started to appear in the CTC authoring templates, when content items are saved. Turns out they’re configured out-of-the box to expect MLS to be turned on, which is nice. The section shows the content you’re viewing and, if a translation exists tells you about its workflow stage and allows you to browse it. If no translation exists (e.g. because this is new content and you have not enabled the workflow to localize the content) then the section presents buttons to clone or link content in the localized library.
In this image, we see the localized (but untranslated) content for one of the entries in the Program section of the CTC Demo website.
One of the unintended consequences of cloning the CTC Demo library is that all of the content items in that library were cloned. The way the demo website is configured, content items are held to control the configuration of things like carousels – when the CTC Demo library is cloned, these content items are cloned too (shown in the image below). This behaviour isn’t “wrong” – there may be circumstances where you would want different configuration per locale. In the case where this behaviour is not desirable then this type of content item should be moved into a library that will not be cloned per locale.