WPML Translations issue

[100leiden]

Hi,

On the page in our secure note we use the text element multiple times on that page . But when we edit the translation only 2 text elements come up for translation. Why is that? When I check the shortcodes in the WordPress editor there isn’t any difference between the shortcodes except for the ID attribute.

Also I don’t see any other elements like headlines, buttons etc. coming through for translation. Why is that?

I can’t make use of the duplication method with the language flags in cornerstone because first of all that’s not maintainable whenever the original language page changes. Second of all we are making use of a translation service through the wpml translation management. So I absolutely need to make use of the translation management.

[ruenel]

Hey @100leiden,

Thanks for writing in! I have checked your page and it seems that you have edited it outside of Cornerstone.

Please use Cornerstone in translating the page. You might need to check this article first:

• https://theme.co/docs/wpml#translation

Best Regards.

[100leiden]

Hi Reunel,

Thanks for your reply!

I didn’t edited the page outside of cornerstone. I only checked if the text blocks had the same shortcodes. Because only 2 of the same shortcodes come through for translations.

The documentation shows a way to duplicate the page and change the text in cornerstone. But that way the translations doesn’t get updated once you make a change to the original language. If we do it like you say it just a copy of the original language. That is not the way it should work. The original language and translations should be linked to eachother so it’s maintainable. That is why we need to make use of the translation management of WPML.

We also make use of a translation service and they work with translation management to push the translations to our website. That way once the original language changes we get a notification in the website that the original language changed and the translations need to be updated.

[christian]

Hey @100leiden,

I checked the page URL and discovered that you’re using V2 or non-Classic Elements. Only the Classic elements work with WPML’s Translation Management. I know Classic Elements are limited but this is only the solution.

Because the non-Classic elements structure are complex, it can’t currently be made compatible with the Translation Managment.

If you wish to see Classic Elements in the builder only, you can choose to disable the Elements (non-Classic is called Elements) in the Permissions page (see https://theme.co/docs/configure-user-permissions).

[100leiden]

Hi Christian,

Thanks for your reply.

There should be some kind of warning or something to make that clear once WPML is installed and activated. We have build more then 3 websites now with non classic elements so we have to rebuild them all over again. With the current layout and design that we build it’s not possible to go back to classic elements.

Is there no way to make those elements compatible with the Translation Management? Isn’t is just updating the wpml-config.xml so all non-classic elements shortcodes are declared in that file?

[christian]

Hey @100leiden,

@100leiden

There should be some kind of warning or something to make that clear once WPML is installed and activated.

Thank you for your feedback. I’ll post this in our issue tracker to let our development team know of your concern.

@100leiden

With the current layout and design that we build it’s not possible to go back to classic elements.

In that case, you will need to do the manual translation method. I understand you said you need to use the translation management but the manual method is your only choice right now.

@100leiden

Is there no way to make those elements compatible with the Translation Management? Isn’t is just updating the wpml-config.xml so all non-classic elements shortcodes are declared in that file?

There is no way to make the elements compatible because their structures are complex.

Thank you for understanding.

[100leiden]

Hi Christian,

What do you mean by their structures are complex? Can you elaborate on this matter? I don’t understand why we can’t declare them in a config file.

Is your team working on making the Translation Management compatible with the new elements? I can’t believe I’m the first with this issue?

[christian]

Hey @100leiden,

Let’s take the Alert and Classic Alert elements for instance.

The Classic Alert content is available in the WordPress content. It’s not the case for the Alert element (orange highlight).

All Classic elements are just simple shortcodes. You can see the shortcode structure in your themes folder \pro\cornerstone\includes\shortcodes. Note that the content of that folder is only for Classic Elements.

The content of the v2 or non-Classic elements is stored and retrieved from the database. As you can see in the screenshot above, it calls the alert content with an ID of 4.

If you want to see the structure of the v2 elements, check this folder themes\pro\cornerstone\includes\elements\definitions

You’ll see that the v2 elements could not if not impossible to be compatible with WPML’s config file.

Maintaining the CornerStone Page Builder (X Theme) Compatibility with WPML -...

---

Our development team’s way of translation is manual. Automatic translation is in our list of feature requests.

Thank you for understanding.

[100leiden]

Hi Christian,

Thanks for the clarification. I still have one more question regarding this:

What’s the difference between these two elements?

Because the first one doesn’t come through for translation but the second one does but they seem exactly the same?

[christian]

Hey @100leiden,

There’s no difference. But, since surrounding those shortcodes are non-Classic shortcodes, that could disrupt WPML translation. Non-Classic elements generally will not work with the Translation Management.

[100leiden]

Hi Christian,

Thanks for your reply! I get it know.

Is there an easy way to export all the text of those new elements with a plugin or something (Maybe WP All Export)? So we can still send it manually to a translation service?

[christian]

Hey @100leiden,

Regretfully, there’s no way to export the text. The Cornerstone content or data is stored as JSON in the wp_postmeta table meta_key column. We can’t export nor read the data.