A third-party shortcode worked on its own, but it did not parse when placed inside a [wpv-conditional] in Elementor, even after being added under Toolset’s third-party shortcode arguments.
Solution:
The issue was caused by the rendering context. Toolset can process registered third-party shortcodes nested inside Toolset shortcodes when they are rendered in a Toolset context such as a Content Template, but not reliably when the raw conditional is placed directly inside an Elementor widget. The solution was to move the conditional and nested shortcode into a Toolset Content Template and then output that Content Template in Elementor. The customer confirmed this worked.
The customer could not translate the HTML content inside a Toolset Layout Visual Editor Cell with WPML. Sending the Layout for translation only showed the title and an “Optional” string, while the Visual Editor Cell content did not appear in translation or in String Translation.
Solution:
It was explained that the HTML inside the Visual Editor Cell was too complex to be detected automatically by WPML. The suggested workaround was to wrap translatable text with the [wpml-string] shortcode so it could be found in String Translation. The customer later used a Content Template instead, reassigned it to the relevant elements, and confirmed that this solved the issue.
