Problem: The client was unable to update the footer translation using the WPML plugin. After translating and saving the footer, it disappeared from the translation management, and the client could not update it. Additionally, the link in the translated footer still pointed to the document in the original language. Solution: 1. We confirmed that the English footer displayed correctly but noted that the Contact Form 7 part was still untranslated. We recommended following the steps in this guide: Using Contact Form 7 with WPML. 2. We noticed that the 'Not Completed' filter was active in WPML >> Translation Management, which hid completed translations. We advised clicking the 'Clear Filters' button to view all items. 3. To address the issue with the incorrect document link: - We navigated to WPML >> Translation Management. - Hovered over the Global Footer template and clicked on the 'Edit' link. - Opened the translated template and updated the Terms and Conditions link. - Pressed the 'Update' button to apply changes.
If this solution does not resolve your issue or seems outdated, we 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.
Problem: If you're experiencing issues where HTML code is displayed instead of normal text in your translated posts on your WordPress site using WPML, such as seeing
<ul> <li>Chambres à coucher</li> <li>Salles de bains</li> <li>Salle de séjour</li> <li>Salle à manger</li> <li>Cuisine</li> <li>Terrasse</li> <li>Parking</li> <li>Piscine</li> </ul>
instead of formatted text, follow these steps to resolve it. Solution: 1. Navigate to WPML > Settings > Posts and pages synchronization and uncheck "Send to translation the content of raw HTML cells". Then, resend the page for translation. 2. Access the body template of your site. Switch to the French version and edit the template. Locate the accordion widget and enable the "RAW HTML" setting.
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. If issues persist, please open a new support ticket.
Problem: The client wants the language menu to appear only on a specific page, despite setting it up, the language menu appears on all pages. Solution: If you're experiencing this issue, we recommend trying the following steps: 1. Add the following CSS to the custom CSS section of your theme to hide the language switcher on pages other than the specified one:
2. If you are using the Dropdown option from the Language menu items style section and want to disable the Current Language option, switch to the List of languages option instead. You can find this setting under WPML >> Languages > Menu Language Switcher. For more detailed instructions, please visit our documentation: How to display or hide the language switcher on specific pages
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. If further assistance is needed, please open a new support ticket.
Problem: The client is experiencing a 500 Internal Server Error on their multilingual e-commerce site when switching to languages other than the default. The issue is causing the site to go down frequently, and sometimes the layout appears broken. The client attempted to resolve the issue by inserting code into the
functions.php
file based on an outdated WPML errata page, but this did not resolve the problem.
Solution: We recommend the following steps to troubleshoot and resolve the issue: 1. Verify that the server meets all WPML minimum requirements by checking our documentation: WPML Minimum Requirements. 2. Consult our FAQ for guidance on resolving 500 errors: 500 Error FAQ. 3. Enable WordPress debugging to gather more information about the cause of the 500 errors: Debugging WPML. 4. Test for a compatibility issue with plugins or themes: - Create a full website backup. - Disable all plugins except for WPML and its add-ons. - Check if the issue persists. - If the issue is resolved, reactivate plugins one by one to identify the culprit. - If the issue still occurs with non-WPML plugins disabled, switch to a default theme like TwentySeventeen and test again. Performing these steps in a staging environment is highly recommended.
If these steps do not resolve the issue or if the solution provided here is outdated or not applicable to your case, 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 you still need assistance, please open a new support ticket: WPML Support Forum.
Problem: The client is trying to translate the global header of their site but when they go to Translations, the header opens in the WPML translator and looks empty. Solution: We noticed that the header contains primarily the Menu, with no additional content, which is why the translation editor doesn't display anything except for the title. Menus should be translated via Appearance > Menus. After translating the menu, it will automatically update in the translated version of the header. We recommend checking our documentation on translating menus: https://wpml.org/documentation/getting-started-guide/translating-menus/
Even if the menu is not translated but only the pages linked to it are, the menu will still appear translated in other languages as long as the header is translated. Therefore, we suggest translating both the header and the pages linked to the menu for the header and menu to display correctly in other languages.
If this solution doesn't look relevant, please open a new support ticket in our forum: WPML support forum.
