Problem: The client needed help configuring the Translation Queue visibility for standard translators in WPML. The goal was for translators with the roles of Subscriber and Translator to only see jobs that are Open/Pending and assigned to them, without seeing jobs assigned to others or the full queue like Translation Managers. Solution: We confirmed that in the default WPML workflow, users with the Translator role should only see translation jobs assigned to them, jobs they have previously translated, or jobs waiting to be taken from the translation queue. If the client observes different behavior, it might be due to modifications in the default WordPress/WPML roles or capabilities by custom code, a plugin, or a role management tool. We also clarified that seeing completed jobs in the queue is expected behavior if the job was originally translated by that translator. This is designed to allow them to edit their specific translations without affecting the entire page or creating a new translation.
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: You are experiencing a loss of metadata, specifically translator comments from XLIFF files, when switching from the Advanced Translation Editor to the standard WordPress editor. This issue arises after clicking "Edit anyway", causing the translation to disconnect from the XLIFF file and resulting in the loss of all translator comments. Solution: Unfortunately, it is technically not possible with WPML to maintain the
<note>
elements from XLIFF files once you switch to the native WordPress editor. Custom development would be necessary to import these
<note>
elements into WordPress metadata or to make them visible in the block editor UI. We recommend setting the translation method on the original content to "WordPress Editor" to prevent overwriting manual translations when later using the WPML Translation Editor. For more details on setting the translation method, please visit: Using different translation editors for different 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 at WPML support forum.
Problem: The client was concerned about managing translation credits between two websites, labmag.ch and labmag.entwicklung.xyz, which appeared to share the same translation memory. Solution: We confirmed that both websites indeed share the same translation memory. Therefore, managing credits for one will affect both sites equally. We advised that it is not possible to remove labmag.entwicklung.xyz from the translation memory as it was the original site where the translation was performed. This setup, where translations are done on a staging site and then moved to production, is quite common. If the client wishes to reorder the websites in the list, they can do so by disconnecting and reconnecting the websites, although this might not be necessary as it does not change the underlying functionality.
If this solution does not resolve your issue or seems irrelevant due to changes in WPML versions or your specific setup, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is experiencing an issue where special characters in taxonomy labels, such as 'Catégorie', are saved incorrectly as HTML entities in the database when using the WPML plugin. This incorrect string is then displayed in both the admin translation editor and on the front end of the site. Solution: We recommend checking the database collation settings. The collation 'utf8mb4_unicode_520_ci' should generally resolve issues with special characters. Additionally, it is crucial to ensure that you have made a full site backup (both files and database) before making any changes to the database settings. If the problem persists or if this solution does not apply to your case, please visit our support forum for further assistance. We also 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.
Problem: The client's homepage is not displaying the translated content in Polish, despite other languages working correctly. Solution: We recommend following these steps to address the issue: 1. Create a full backup of your site. 2. Update all outdated plugins, themes, and the WordPress core to the latest version. 3. Apply the workaround described on the errata page. 4. Edit the homepage in the original language, make a small change in the content, save these changes, and update the translations. 5. Ensure the Polish translation is published by going to Pages -> Filter by the Polish language -> Search for the homepage translation and double-check it.
If these steps do not resolve your issue, or if the solution 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 at WPML support forum.
Problem: You are trying to ensure that all links on your homepage are available in the WPML Translation Editor and want to deactivate automatic translation to handle translations manually. However, not all links, such as the 'Fragen' button, are showing up in the Translation Editor. Solution: To make all links available for translation and manage them manually, follow these steps: 1. Navigate to WPML -> Settings -> Custom XML Configuration. 2. Add the following code to include Elementor widgets like buttons and headings for translation:
3. Make a minor change (like adding an empty space) to the original footer or any page you want to translate the link and save it so WPML sees the translation needs an update. 4. Edit the translation, and the links will be available for translation. If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/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 recommend opening a new support ticket at WPML support forum.
Problem: If you're experiencing duplicated menu items in the secondary language when using Elementor, even after manually rebuilding the menu, this might be due to an interaction issue with other plugins or the theme. Solution: We recommend that you first check if the issue persists when only WPML plugins are activated. This will help determine if there is an interaction issue with other plugins. Additionally, try switching your theme to a WordPress default theme like Twenty Twenty. This step will help identify if the issue is related to your current theme.
If these steps do not resolve the issue, it 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
