Problem: The client was experiencing issues with the French version of their website not matching the English version in terms of design and content. Specific problems included missing elements like the mega menu header, language switcher, and various template links and designs. Solution: We recommended the client to manually review all Elementor templates by accessing Elementor Library and confirm the translations. After reviewing, we asked the client to recheck the French homepage for any improvements. Additionally, we provided instructions on translating the menu, which can be found here: Translating Menus. For the styling issues with the language switcher, we inserted custom CSS code into WP > Appearance > Customize > Additional CSS:
Here is your updated code with all ` ` tags removed:
If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at WPML 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 WPML Support Forum.
Problem: The client reported multiple issues with WPML settings: automatic translations were not fully functioning, some items were greyed-out as not translatable, and the WP Menu Sync feature was not working. Additionally, there were problems with translations not appearing in posts and menus. Solution: 1. We addressed the WP Menu Sync issue by recommending the use of an alternative method for translating menus, which can be found here: Translating Menus Documentation. 2. For the greyed-out widgets and settings, we activated the automatic translation and verified the settings to ensure they were configured correctly. We also clarified that some items are intentionally not translatable as per design.
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.
Problème : Vous utilisez theme.co pro et cornerstone pour créer votre site et rencontrez des problèmes lors de la traduction des pages en français. WordPress plante lors de la tentative de traduction, et bien que la page traduite semble exister, elle plante à nouveau lors de l'ouverture. Solution : Nous avons examiné votre configuration et suspectons que le problème pourrait être lié à la politique CORS, surtout si vous utilisez des domaines différents pour chaque langue. Votre hébergeur pourrait confirmer si les paramètres CORS sont correctement configurés. Malheureusement, si CORS est en effet le problème, cela ne peut pas être résolu directement par WPML car cela concerne uniquement les paramètres CORS sur votre serveur.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de vérifier la version des correctifs permanents et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
Problem: The client was experiencing a 503 error in WordPress when using WPML, along with a PHP Fatal error related to the function
get_requested_lang()
. After reinstalling WPML, a new error appeared regarding the premature loading of translations, indicated by the function
_load_textdomain_just_in_time
. Additionally, the client noted slow loading times in the WooCommerce settings when WPML was active. Solution: We identified that the issues were not directly caused by WPML but were related to the latest changes in the WordPress core and possibly other third-party plugins or themes. We recommended the following steps: 1. Check the errata page for known issues: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/ 2. Re-upload the WPML plugin to ensure all files are correctly installed. 3. Create a full site backup before making any changes. 4. If the problem persists, we recommended opening a new support ticket for further assistance.
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: The client is experiencing issues with logging into their WordPress admin in different languages and editing translated pages using Elementor and Yoast SEO. They encounter a redirection issue where the login page switches domains, and credentials do not work unless the browser cache is cleared. Additionally, when editing translated pages, Yoast SEO does not appear in Safe Mode, and a PHP deprecated error related to the rtrim() function is displayed.
Solution: We recommend the client to ensure that their browser cache is cleared regularly to prevent login issues. For the PHP deprecated error, it is advisable to check the PHP version and update it if necessary, as older versions might not fully support current WordPress functionalities. Regarding the issue with Yoast SEO not appearing in Safe Mode, this is expected behavior as some plugins are disabled in Safe Mode to ensure stability and performance. If editing with Elementor is required for translated pages, we suggest contacting Elementor support for compatibility assistance with WPML, as Elementor may not inherently support editing WPML-generated translations.
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.
