Page builders translation does not handle nested shortcodes

Overview of the issue

In some cases, using page builders can produce nested shortcodes. Currently, integration of WPML with page builders does not separate the translation of these nested shortcodes from their parent ones.

Let’s consider a simplified example.

[shortcodeA att1=val1 att2=val2]
  Some text

  [shortcodeB att3=val3 att3=val3]Some nested content[/shortcodeB]

  Some more text
[/shortcodeA]

In this example, we should be able to translate the “Some text” and “Some more text” strings, while the nested shortcode (shortcodeB) should be available for translation as a separate field.

This feature will be added in the upcoming version of WPML.

Workaround

As a workaround, you can still manually translate the nested shortcode (i.e. shortcodeB) by changing its attributes and content in the translation editor, when translating the parent shortcode’s content (i.e. shorcodeA).

You can see an example of this in the following image.