Problem: The client is experiencing an issue where Elementor content does not appear in the WPML Advanced Translation Editor (ATE). Only the Title, Tags, Media titles, and Yoast SEO fields are visible in ATE.
Solution: We found that the issue was due to the Elementor content being added as HTML which was incorrectly formatted. We corrected the issue by editing the content and removing the problematic style part from the HTML. We recommend checking if the Elementor content is added correctly and ensuring that no HTML errors are present. If you want to add styles, please use the CSS tab in Elementor.
Please test this solution on another page to see if it resolves the issue. If the problem persists or if this solution does not apply 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing an issue where your translated page in Spanish shows incomplete content despite being fully translated in the WPML Translation Editor, and the translation job remains 'In Progress', this might be similar to a recent case we handled. The client had a Service page (Warehousing & Storage) that displayed full content in English but only a portion in Spanish. The issue persisted even though the WPML Translation Editor showed 100% completion, and it started after an update to the CMSMasters Elementor Addon.
Solution: We recommend checking if the section causing the issue is correctly added and translated. In the recent case, we resolved the problem by re-adding the problematic section and translating it again to Spanish. This approach successfully finalized the translation job and displayed the full content on the frontend Spanish page.
Please note that this solution might be irrelevant if it's outdated or not applicable to your specific 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 issue persists, please open a new support ticket.
Problem: The client is experiencing issues with WPML and Elementor Pro on their multilingual site. Specifically, translated pages are not applying Elementor templates correctly, and Forminator forms are not being detected by WPML for translation.
Solution: For the Elementor template issue, we recommend setting the '_cmsmasters_locations' custom field to 'Copy' at WPML > Settings > Custom Field Translation. Then, update the original template and re-translate using the WPML Translation Editor to ensure the template's location rule copies correctly. If issues persist, it may require compatibility adjustments from the theme or plugin developers. For more details, revise the last comment on this ticket.
For Forminator, as it lacks WPML integration, create separate forms for each language and manually use the shortcode on the respective pages. Consider scanning the plugin for strings at WPML > Theme & Plugin Localization and translating any detected strings at WPML > String Translation. Alternatively, explore other form plugins compatible with WPML, listed here: https://wpml.org/plugin-functionality/form/
If these solutions do not resolve the issues or seem 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 problems persist, please open a new support ticket at our support forum.
Problem: The client reported an issue where the confirmation modal for the 'Redirect visitors based on browser language only if translations exist' setting in WPML does not close or save after clicking 'Got it, activate anyway'. This problem persists across different browsers and in incognito mode, with no visible JavaScript errors. Solution: We replicated the client's site locally and discovered that the issue was related to specific plugins from Hostinger, which are only intended for use on Hostinger servers. We recommend the following steps: 1. Temporarily disable the Hostinger plugins. 2. Try enabling the WPML setting again. 3. Re-enable the Hostinger plugins. If the problem continues, consider setting up a staging site on your Hostinger server and provide us with access to further investigate.
Please note that this solution might be outdated or not applicable to your specific 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 issue persists, please open a new support ticket at WPML support forum.
