Problem: You are using the Avada WP Theme and have set up FAQs in the WP Admin table. While the FAQ element displays correctly in English, it fails to appear in the French version for one specific FAQ. Solution: We found that the issue was due to an incorrect slug in the French translation of the FAQ Categories. The slug was set to 'bobines-induction' but should be 'bobine-de-scellage'. We recommend updating the slug to the correct one, saving the changes, and then testing the page again. This solution was verified on a staging site.
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.
Problem: If you're experiencing an issue where your website's German translations have been replaced with French translations, and this change occurred sometime between May and September, and it's not visible on the Wayback Machine, we can help you address this. Solution: First, ensure you create a full backup of your site. This is crucial to avoid any data loss. Next, navigate to Plugins -> Add new -> Commercial tab, and upgrade all your WPML plugins to the latest version. Then, go to the page that shows incorrect translations, such as the one you mentioned, and make a small edit to the content in the original language. Save these changes and update the translation. This process might resolve the translation mix-up. If the issue persists or the solution provided here becomes irrelevant due to updates or it simply doesn't apply to your case, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Additionally, if you need further assistance, please open a new support ticket.
Problem: The client is experiencing 502 bad gateway errors on their site. The hosting provider identified that the 'wp_installer_settings' from wpml-string-translation is maxing out the autoload options, contributing significantly to the issue. The client is considering turning the autoload to OFF for 'wp_installer_settings' and 'wpml_strings_need_links_fixed'. Solution: We advised the client against disabling the autoload for 'wp_installer_settings' and 'wpml_strings_need_links_fixed' as it is not recommended. Instead, we suggested the following steps to diagnose and potentially resolve the issue: 1. Create a full site backup. 2. Update any outdated plugins or themes. 3. Flush any cache memory. 4. Activate WordPress debug mode as described in this guide. 5. Deactivate all plugins, including WPML ones, and activate a default WordPress theme like Twenty Twenty. 6. Reactivate the WPML plugins and then activate the theme and other plugins one by one to identify the culprit. 7. Check for any fatal errors in the debug.log file within the wp-content folder. Additionally, we informed the client that the next WPML version (v4.9) will have a much smaller 'wp_installer_settings', although there is no estimated time of arrival for this update.
If this solution does not resolve your issue or seems irrelevant due to being 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 issues persist, please open a new support ticket.
Problem: The client is experiencing issues where an updated image on the base language page is not reflecting in the translated versions (e.g., French). Additionally, despite previous complete translations, the WPML ATE editor shows incomplete translations and requires re-translation of content that hasn't changed. Solution: 1. If you're experiencing similar issues with image updates not reflecting in translated pages, we recommend making a minor edit to the base language page (like adding an extra space) and then saving it. This should prompt an update requirement for the translations. 2. Re-edit the translation to ensure it reaches 100% completion. This process helps in syncing all content, including any text associated with images. 3. If the WPML ATE editor does not recognize previously translated content, it might be due to the content being translated using a different editor (like the Classic Translation Editor or manually via the WordPress editor). In such cases, ATE cannot reuse translations as it relies on its own translation memory stored on servers. 4. To resolve this, continue using the original translation method (Classic Editor or WordPress editor) that was used initially. If you switch to using the ATE editor for future translations, it will store and reuse translations automatically for subsequent changes. For further guidance, refer to these documentation links:
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. Should issues persist, please open a new support ticket at WPML support forum.
Problem: You are trying to ensure that the top section of your homepage is correctly translated into French using WPML. Although the translation appears correct in the WPML Translation Editor, it does not display on the French version of the homepage, and the styling differs from the English version. Solution: We recommend editing the homepage in the primary language, English, and then resaving the page. Afterward, retranslate the contents. This process should ensure that both the translation and the styling are correctly applied to the French version of the page. 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 for further assistance at WPML support forum.
