Cornerstone and WPML status 2025

[Regnalf]

I’m currently struggling through the forum and the documentation regarding WPML and Cornerstone. Unfortunately, I’m still a bit confused as to what the latest status is.

As far as I understand it, there should be 4 ways to translate pages:

1 - With the Cornerstone Editor language switcher it is possible to copy the entire page and adapt the texts manually. This would most likely only be necessary if images containing text had to be translated. Correct?

2 - With the WPML Advanced Translation Editor which recognizes text blocks and translates them line by line.

3 - With the string translation plugin which can also translate texts from a language file such as .po. According to @Charlie (WPML in 6.5.0) it should also work with twig and this shortcode, {{ __('My Content', 'my_localize_domain') }} but I didn’t get it to work. (I assume that this does not work with the String Translation plugin, unless you create a real .po file in the theme folder.)

4 - With the WPML shortcode and string translation [wpml-string context=“my-domain” name=“my-name”]My string[/wpml-string]. Warning, if automatic recognition is activated, countless unfinished entries can be created during runtime as Cornerstone updates the page in the background. It is best to first create the prefabricated shortcode in another editor and then insert it.

---

You can use the WPML Advanced Translation Editor to translate normal text elements. But I tried it with a button, and the text is not read from there. Does this currently only work with normal text elements?

Components should still be processed with the Cornerstone language switcher, correct?

Thanks in advance

Regnalf

By the way, I already use the HTML mode in Cornerstone.

[christian]

Hey Regnalf,

@Regnalf

You can use the WPML Advanced Translation Editor to translate normal text elements. But I tried it with a button, and the text is not read from there. Does this currently only work with normal text elements?

Yes, that works only with Classic Elements but please try copying your site to a staging server and in the staging try converting your content to HTML storage. Please let us know how this goes.

@Regnalf

Components should still be processed with the Cornerstone language switcher, correct?

As of now, you need to have 2 Components. One for each language. You need to add the applicable Component to your translated layout.

[Regnalf]

Hi christian

@christian
… try converting your content to HTML storage …

I already wrote that i’m in HTML Mode, and i startet this fresh new page in that mode.

The Test page with one Text Element and one button

button text:

The editor window

here ist the html code from database

  <!-- cs-content --><div class="x-section e887-e1 mon-0"><div class="x-text x-content e887-e2 mon-1">Mein Text in Deutsch</div>
<a class="x-anchor x-anchor-button e887-e3 mon-2" tabindex="0" href="#"><div class="x-anchor-content"> 
  <div class="x-anchor-text"><span class="x-anchor-text-primary">Zeile eins</span><span class="x-anchor-text-secondary">Skundäre Zeile</span></div></div></a>
</div>
<!-- cs-content-end -->

The primary text seems to be recognized, the secondary line not.

[christian]

Apologies for missing that @Regnalf.

Thanks for showing the content. WPML would be able to translate the HTML content now. I believe it just needs extra setup like in this WPML thread https://wpml.org/forums/topic/translate-custom-html/

It would be best that your reach out to WPML support to learn how to translate the HTML content.

The purpose of the HTML content is for 3rd party plugins to access Cornerstone’s output. We, however, cannot support how the 3rd party plugins will process the HTML content.

[Regnalf]

Thanks @christian,

I have created a support ticket at WPML, because it is strange why the first element is recognized and the second is ignored. There is nothing unusual about the HTML code.

I’ll let you know what the results are.

[tristup]

Hi @Regnalf,

Thanks for informing us, will wait for the response.