Problem: You are using Bricks builder 1.10.3 and WPML, and you encounter an issue where the Dutch translation of a page appears empty even though it has been translated. Solution: We recommend checking the workaround on this page. First, disable the "I prefer bigger segments" option. Then, update the page in the default language and subsequently update its translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with saving special characters and flags in WPML while using Elementor. The special characters and flags are not displayed correctly after being saved. Solution: We recommend switching to the previous version of the Advanced Translation Editor to resolve this issue. Here are the steps to follow: 1. Go to the top right corner of the translation editor. 2. Click the gear icon. 3. Enable the option "Use the previous version of the Advanced Translation Editor." Please try these steps and check if the special characters and flags display correctly.
If this solution does not resolve your issue or 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 do not hesitate to open a new support ticket at our support forum.
Problem: The client was having issues with an archive page created with Bricks builder, where they used a loop to display categories and dynamic data to call the featured image from an Advanced Custom Fields (ACF) field for custom taxonomy types. Solution: We recommended the client to manually edit the translated taxonomy that was causing the issue and simply click save. This action should resolve the problem with the display of the translated taxonomy.
If you're experiencing a similar issue, we recommend you try manually editing the translated taxonomy and saving it. However, this solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, 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 you still need assistance, please open a new support ticket at our support forum.
