Problem: The client needed to determine if their site uses Twig templates for the WPML language switcher, as they received a notification about changes related to Twig. They provided code snippets and details about their implementation, which they did years ago and were unsure about the current setup. Solution: We advised the client that the code they shared indicates a PHP-based implementation of the WPML language switcher, not a Twig-based one. Therefore, their current setup should not be affected by the changes related to Twig templates. We recommended that they ensure they have a full website backup as a precaution. Additionally, we confirmed that all links shared in the support ticket are private and only visible to the client and the support team.
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.
Problem: The client is trying to display a page in Spanish, but it appears in English. The translation job was incorrectly marked as 'Spanish > English' instead of 'English > Spanish', and the client wants to reassign this page to a Spanish translator. Solution: 1. Disconnect the page translation from the original by following this guide: https://wpml.org/faq/how-to-disconnect-translations-from-the-default-language-page-or-post/. 2. If the English post is currently in Spanish, change the "language of this post" to English. 3. Proceed with the translation. Alternatively, if the page's original language is Spanish and the English version is a translation from Spanish: 1. Select "Edit anyway". 2. In the drop-down menu labeled "This is a translation of," choose "None". 3. Repeat this process for the French and Italian versions. 4. Reconnect the pages, setting English as the default language. 5. Make a minor change to the English page and update it. 6. Resend the page to the Spanish translator from WPML → Translation Management.
If these solutions do not apply to your case, or if they 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 issues persist, please open a new support ticket at WPML support forum.
Problem:
On the front end of the site, I still see 'Deck Lights' in English when switching to Spanish, despite adding the translation in 'String Translation' and emptying all caches.
Solution:
The strings from the client's code were missing a text-domain.
Adding the missing text domain in the header.php code resolved the issue.
Problem: The client is experiencing database errors related to collation issues in their WordPress error log, which mention WPML.
Solution: We recommend ensuring that all database tables and their columns have a consistent collation. Specifically, change any tables or columns with the collation "latin1_swedish_ci" to a unicode-aware collation such as "utf8mb4_unicode_ci" or "utf8mb4_unicode_520_ci". For WPML tables, use the "Fix WPML table collation" option available under WPML → Support → Troubleshooting. WPML Troubleshooting Options
If you're not comfortable making these changes yourself, you can ask your hosting provider for assistance. It's crucial to back up your database before making any changes. You can find more information on changing collation in the database here: Stack Overflow: Change Character Set and Collation
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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. If necessary, do not hesitate to open a new support ticket with us.
Problem: The client manually replaced content on different language versions of a page and noticed that the live page got replaced by old outdated content after clicking the translation editor. The client also experienced issues with HTML formatting in the translation editor and had concerns about the workflow for updating translations and translating widgets.
Solution: 1) If you're experiencing issues with your manual content being overwritten after using the WPML Translation Editor, we recommend that you consistently use one method for translations. If you've started with the WordPress editor, continue using it to avoid losing your translations.
2) To switch to the WordPress Editor: - Go to the Language section in the sidebar. - Click to switch to the WordPress Editor. - In the pop-up dialog, select 'This page' and click 'Apply'. For more details, please check: Using Different Translation Editors for Different Pages.
3) If you decide to use the WPML Translation Editor and need to update HTML formatting, you can do so directly within the editor. For guidance on managing HTML in the Translation Editor, please refer to: HTML Markers in Advanced Translation Editor.
4) To disconnect a translator from a task: - Go to WPML > Translation Management. - Find the job under the 'Jobs' tab. - Cancel the job if it's still assigned to a translator. For more information, please visit: How to Cancel Translation Jobs.
5) For translating widgets, you can either use 'WPML > String Translation' or create a widget for each language. For a step-by-step guide, please see: Translating Widgets.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, 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 need further assistance, please open a new support ticket: WPML Support Forum.
