사용 가능한 솔루션

Problem:
The client is experiencing issues with links not being translated correctly, resulting in 404 errors or linking to the wrong language version of the page.

Solution:
We recommend two approaches to resolve this issue:
1. As a long-term solution, add

<type="link">

to your existing XML configuration. This will ensure that links are correctly translated.
2. As a short-term solution, use machine translation for the URLs and manually edit the translations if they are incorrect.

We advise the client to implement the first solution for a permanent fix. However, it is important to note that updating existing pages that use shortcodes from the previous XML configuration will be necessary to make the changes effective.

If this solution does not seem relevant to your situation, please open a new support ticket with us.

Problem:
If you're using WPML with Bold Builder and encountering issues where custom element translations made directly on Pages are erased when using the WPML translation editor, this might be due to the elements not being registered as translatable.
Solution:
First, ensure that the custom elements are registered in WPML to be translatable. You can do this by adding the necessary XML configuration in WPML-> Settings-> XML Configuration. Here is an example of how to register a custom element:

<wpml-config><br />    <shortcodes><br />        <shortcode><br />            <tag>bt_bb_headline</tag><br />            <attributes><br />                <attribute encoding="allow_html_tags">headline</attribute><br />                <attribute encoding="allow_html_tags">subheadline</attribute><br />            </attributes><br />        </shortcode><br />    </shortcodes><br /></wpml-config>

For more details on registering page builder elements, check this guide: https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/
Additionally, if you notice that certain elements like button texts disappear from the editor, it might be due to incorrect tags in the plugin's XML configuration. For instance, replacing

<tag>bt_text</tag>

with

<tag>bt_bb_text</tag>

in the plugin's XML file can resolve this issue.

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket at https://wpml.org/forums/forum/english-support/.

Problem:
The client was experiencing issues with WPML updates failing due to the hosting server's inability to whitelist certain domains necessary for the updates.
Solution:
We recommended that the client ask their hosting provider to whitelist the domains: wpml.org, cdn.wpml.org, and api.wpml.org. Additionally, updating OpenSSL on the server might resolve the issue. If the hosting provider is unable to whitelist these domains, we suggested manually updating WPML by downloading the latest versions from https://wpml.org/account/downloads/ after creating a full website backup and removing the existing WPML plugins. Alternatively, changing the hosting provider could be considered.

If this solution does not apply to your situation, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket at WPML support forum for further assistance.