WPML w/ Components & Parameters

Support
#1

I’m trying to figure out how to handle translations for my new WPMU build, w/ Components & Parameters. Is the Advanced Editor the only method for this task?

I’m not seeing very recent posts for answers, but I can’t help but notice the “Deprecated as of CS 7.8.0”.

Please suggest how I should move forward.

Advanced Editor

The Advanced Editor is being deprecated as of Cornerstone 7.8.0. This system will have numerous flaws when it comes to making changes to the source language. As a result WPML and Themeco does not recommend using this system. This system will still be in place as we work out potential issues. In the Cornerstone settings you can enable this editor in the Advanced tab under WPML Advanced Builder . Sites upgrade from previous versions will have this setting on by default.

#2

Hello @splaquet,

Thanks for writing in!

As you noted, the Advanced Editor was deprecated as of Cornerstone 7.8.0. This system has numerous flaws, particularly when making changes to the source language. As a result, both WPML and Themeco do not recommend using this system.

The supported and recommended method is to use WPML’s String Translation or WPML’s Translation Management to translate the content within your Components and Parameters. Here is a general workflow:

  1. Translate the Component’s Content: Use WPML’s Translation Management to send the page or template that contains your Component for translation. This will allow you to translate the text strings inside the Component’s elements.
  2. Translate Parameters via WPML: If your Parameters contain translatable text (e.g., dynamic strings), you can manage these through WPML’s String Translation module. This allows you to find and translate strings that are not directly part of the page content.

  • Do not enable the Advanced Editor in your Cornerstone settings (found under Cornerstone > Settings > Advanced). Sites upgrading from previous versions may have this setting on by default, so we recommend disabling it.

  • Use WPML’s standard translation workflows for all your content, including Components. This is the most stable and future-proof method.

  • :open_book: Official Documentation – WPML Integration (Please refer to the documentation for detailed steps on translation workflows).

If you need more specific guidance on setting up WPML for your Components, please provide details on your translation workflow (e.g., manual translation, using translation editors) and your System Info.

Thanks.

#3

There’s obviously a step that I’m missing, because I cannot seem to find component strings anywhere. Similar to another post on this forum, the only translation field that appears when working on a page is the page title.

I’ve gone into settings and added Components as Translatable, activated “Detect strings in JavaScript files”, viewed the pages… still only seeing the 1 Title field available for translation.

I looked on WPML’s support forum and found a few others with the same question, but support hasn’t responded to any of their requests.

What’s the process of fetching the components content and populate the string translation or post translation?

Just in case it’s not a simple explanation, I’ve added login credentials to a secure note.

#5

Any explanation on why WPML isn’t pulling strings from my pages or Components? I can go to WPML support if it’s on them, but I have a feeling this is a theme issue.

#6

In WPML 5.0 they are releasing support for layout translations. When that is launched we will be working with them to get Components translatable. You can reach out to them on the status as well.

#7

amazing! I just installed WPML v5. I’ll see if I can figure this thing out.

#8

Good to know that, @Splaquet. Cheers.

#11

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.