Problem: After a recent update, you can no longer change the HubSpot form ID for translations as you used to. This issue arises when trying to translate HubSpot forms on multilingual sites using WPML. Solution: We recommend the following steps to resolve this issue: 1. Navigate to WPML >> Settings > Custom XML Configuration section and add the following XML:
2. Use the HubSpot form widget instead of the default shortcode widget. 3. Attempt to translate the page again and check if the issue is resolved.
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 the problem persists, please open a new support ticket.
Problem: The client is unable to translate text formatted with ElementsKit's custom syntax using curly braces ({{ }}) in the Advanced Translation Editor (ATE). The error message indicates that 'the original sentence includes formatting markers.' Previously, these could be translated without issues. Solution: We recommend avoiding the use of ElementsKit's curly-brace formatting for now. If you need to emphasize parts of a heading or text, consider using standard HTML tags like strong or span with a CSS class for bold styling. This method is more likely to be parsed correctly by ATE. We are currently monitoring the situation and will update you if any fixes become available.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
