Problem: The client was experiencing an issue where Elementor icons were not visible on translated pages, displaying as empty rectangles instead. Despite updating WPML plugins and regenerating Elementor CSS, the problem persisted. Solution: We identified that the issue was due to CORS restrictions, with Elementor's Font Awesome files being loaded from a different domain than the page. We recommended the following steps: 1. Go to Elementor → Tools. 2. Click Regenerate CSS & Data. 3. Clear all caches: WordPress cache, server cache, CDN cache, and browser cache. 4. If the issue persists, ask the hosting provider to add a CORS rule for font files:
Additionally, ensure that the secondary language page loads Elementor assets from the same domain as the current language.
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. If needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where the Complianz cookie banner displays only Slovak text across all language domains despite having translations available in WPML String Translation. This issue persists even after multiple troubleshooting steps, including rescanning plugin strings, purging caches, and testing in different configurations.
Solution: We recommend checking the compatibility of Complianz with the WPML 'different domain per language' setup. It's important to ensure that all strings are correctly translated and rescanned in WPML. If the problem continues, try the following steps: 1. Change the URL format to 'Different languages in directories' temporarily to check if the issue is related to domain configuration. 2. If the issue persists, it might be a deeper compatibility issue or a problem with how Complianz handles default language content. In this case, further investigation into the plugin's interaction with WPML is necessary. 3. Consider testing on a minimal setup or a clean installation to isolate the issue. 4. Review the related known issues on WPML Errata and follow any relevant solutions.
If these steps do not resolve the issue, or if the solution provided here becomes outdated, we highly recommend opening a new support ticket. Also, check the related known issues on WPML Known Issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please contact our support team at WPML Support Forum.
Problem: The client was unable to translate media files using WPML as the page displayed a 'setup required' message without any actionable buttons to proceed. Solution: The issue resolved itself when the client attempted the process again the following day and successfully clicked on 'finish setup'. If you're experiencing a similar issue, we recommend trying to access the setup again. If the problem persists, ensure that your WPML and other plugins are up to date. It's also advisable to check for any known issues related to media translation at WPML Known Issues.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, please do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: The client reported that custom fields in the 'Projects' custom post type (CTP) were not visible when opening any of the posts, despite the data existing in the table. Solution: We reviewed the issue and discovered that the visibility problem was related to the theme's user interface rather than WPML. The custom fields were hidden within a collapsed accordion/tab in the Meta Boxes section at the bottom of the editor. By expanding the Meta Boxes section, the Project Details fields became visible in both languages. If you're experiencing this issue, we recommend checking the Meta Boxes section in your post editor and ensuring that all necessary tabs or accordions are expanded.
Please note that this solution might be irrelevant if it's outdated or not applicable 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. If the problem persists, please open a new support ticket at WPML support forum.
Problem: While adding English translations to a Dutch website, raw code appeared in the footer, specifically resembling Elementor widget data. Solution: 1. Navigate to Templates → Theme Builder or Elementor → Templates and locate the footer template. 2. Switch to the English translation of the footer. 3. Open it with Elementor and inspect the Navigation/Menu widgets. 4. Remove any visible raw code/text and re-add the menu widget if necessary. 5. Save the footer translation and clear all caches. 6. If the footer text is not available in the Translation Dashboard, check it in WPML → String Translation after scanning the theme/plugin strings. For more details on translating theme options, visit https://wpml.org/documentation/getting-started-guide/string-translation/how-to-translate-theme-options/
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. If further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
