WPML String Translation support for Cornerstone V2 Elements

[skndal]

Hey guys,

Several of the Cornerstone-powered website’s I’ve been managing are growing and changing at a pace that makes it impossible to manually translate and update each page individually. WPML makes our life easy by offering a String Translation functionality where we only have to edit/update the text strings contained within each element of page content. This has worked like a charm for older versions of Cornerstone more than a year ago…

Unfortunately with the new updates and the (awesome!) V2 elements, WPML’s string translation functionality is completely broken. It doesn’t recognize the content inside V2 elements at all. Nonetheless, it is one of the most popular and powerful multilanguage tools for WordPress websites, and compatibility should be expected of a strong theme/plugin like X/Cornerstone.

What kind of timeline can we expect for String Translation compatibility for V2 Elements?

I’ve been a huge fan am running tons of sites on X, but if this issue doesn’t resolve I’m gonna have to rethink its use for multilingual sites. To put it simply: manually creating and updating page translations will not cut it.

If you could help escalate this issue you’ll make a lot of us building multilingual websites very happy.

(Link: https://wpml.org/errata/cornerstone-shortcodes-arent-rendered-in-the-translated-pages/ )

[christian]

Hey Meng,

We appreciate your feedback. However, this does not need to be escalated because our development team already knows this concern.

Regretfully, we do not have a timeline when V2 elements will be compatible with WPML. There is a technical hurdle that makes String Translation currently not possible.

For now, you will need to stick to using Classic Elements including Classic Sections. If you’re not aware how to add a Classic Section yet, please watch this screencast: https://youtu.be/EZ0CJWUarmo

Thank you for understanding.