We’re using WPML on a page that contains a normal shortcode string inside page content, for example:
[fluent_booking id="68"]
On the translated Spanish page, we need that to become:
[fluent_booking id="69"]
This should be a simple translation/use-case. From the page-content side, this is just shortcode text stored in the page until WordPress renders it. It should not require us to fight with custom XML rules, numeric-field handling, shortcode registration, or special packaging logic just to swap one shortcode string for another on a translated page.
We followed your documentation for translating custom shortcodes and numeric values, including custom XML configuration, but WPML still showed 0 words to translate and did not expose the shortcode in the translation flow.
The real issue is not just this one shortcode. The issue is that WPML does not provide a simple page-level mechanism for us to explicitly say:
“On this page, treat this exact text/string/shortcode as translatable and let us define the translated version.”
That kind of override should exist in the UI without needing XML. A straightforward string-mapping or page-level manual translation override would solve this immediately and would be much more practical than the current logic.
For now, we are forced to manually re-edit the Spanish page after retranslations, which defeats the purpose of using WPML for this workflow.
Please advise:
1. Is there an officially supported way to force a shortcode string like this to appear in translation for a specific page?
2. If not, can this be submitted as a product improvement request for a page-level/manual string mapping feature?
3. Why does WPML ignore a shortcode string in page content even after following the shortcode translation documentation?
This feels much more complicated than it should be for a normal multilingual page workflow.
