[Resolved] Link encoding issues

The WPBakery page builder encoding attributes usually should work with the encoding="vc_link" attribute as mentioned in our doc: https://wpml.org/documentation/support/language-configuration-files/register-page-builder-content-for-translation/

So, I updated the XML with this attribute in WPML >> Settings > Custom XML Configuration:

<wpml-config>
  <shortcodes>
    <shortcode>
      <tag>vc_btn</tag>
      <attributes>
        <attribute encoding="allow_html_tags">title</attribute>
        <attribute type="link" encoding="vc_link">link</attribute>
      </attributes>
    </shortcode>
    <shortcode>
      <tag>vc_link</tag>
      <attributes>
        <attribute encoding="allow_html_tags">title</attribute>
        <attribute type="link" encoding="vc_link">link</attribute>
      </attributes>
    </shortcode>
    <shortcode>
      <tag>features_carousel</tag>
      <attributes>
        <attribute type="area" encoding="urlencoded_json">box_repeater_items</attribute>
        <attribute type="link" encoding="vc_link">link</attribute>
      </attributes>
    </shortcode>
  </shortcodes>
</wpml-config>

When I apply this encoding attribute the default WPBakery page builder button elements show correctly in WPML Advanced Translation Editor but the custom-built features_carousel Links remains as it is. I tried to update the features_carousel link translation and it was working correctly as you can see in the below links.

Default language: hidden link
Secondary language: hidden link

As the issue is arises in a custom-built element, it would consider the custom programming work, which is beyond the scope of our support. At this point, I would suggest you consider contacting one of our certified partners from this link: http://wpml.org/documentation/support/wpml-contractors/ You will get the custom assistance you need to get on with your project.

I am sorry, I couldn't be much help here.

Thank you for your cooperation and patience

I understand your concerns. While WPML aims to be fully compatible with WPBakery, our primary support is for standard functionalities, and custom coding falls outside our regular scope. I appreciate your point about documentation and will certainly forward your feedback.

To ensure you get the best assistance, I'm going to escalate this issue to our 2nd tier support for further review. They'll assess the situation and provide guidance or suggestions as needed.

Thank you for your patience and understanding