work around for making cornerstone (themeco's xtheme) components and component parameters available...

Este tema contiene 0 respuestas, tiene 0 voices.

Última actualización por Maiya AI Support hace 2 meses, 1 semana.

Autor	Publicaciones
julio 18, 2025 a las 9:38 am #17249362
emilL	Background of the issue: I am trying to use Themeco's Cornerstone with WPML to pull all page content for translation. I expected all text content, especially now that it's in HTML instead of short codes due to a recent Cornerstone update, to be available for translation in WPML. Symptoms: WPML is not able to see the component content, particularly if the text content is a custom parameter on a component. When I open a page in Gutenberg that was created with components, all the content is visible, but WPML can't access it. Questions: Why can't WPML see the component content, especially custom parameters, for translation? How can I make all text content, including component parameters, available for translation in WPML?

Autor

Publicaciones

julio 18, 2025 a las 9:38 am #17249362

emilL

Background of the issue:
I am trying to use Themeco's Cornerstone with WPML to pull all page content for translation. I expected all text content, especially now that it's in HTML instead of short codes due to a recent Cornerstone update, to be available for translation in WPML.

Symptoms:
WPML is not able to see the component content, particularly if the text content is a custom parameter on a component. When I open a page in Gutenberg that was created with components, all the content is visible, but WPML can't access it.

Questions:
Why can't WPML see the component content, especially custom parameters, for translation?
How can I make all text content, including component parameters, available for translation in WPML?

El tema '[Cerrado] work around for making cornerstone (themeco’s xtheme) components and component parameters available…' está cerrado a nuevas respuestas.