Problem: The client is experiencing an issue where deleted glossary entries in Portuguese reappear and do not trigger a retranslation to the default language. Additionally, the slug remains unchanged, maintaining the original translation. This issue persists even after adding a new language (Turkish), where the glossary automatically filled itself with translations using the original term as the translated term. Solution: We have addressed the issue by deleting the problematic glossary entry completely and then re-adding it with only the Dutch value. This approach seems to prevent the Portuguese term from reappearing. We recommend checking if this solution holds by monitoring the glossary entries. If the issue persists or if similar problems occur, especially after activating ATE or adding new languages, we suggest opening a new support ticket for further investigation. Additionally, it's important to ensure that all themes and plugins are updated to their latest versions.
Please note that this solution might become irrelevant due to updates or specific circumstances not covered here. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix. If the problem persists, do not hesitate to open a new support ticket at WPML support forum for personalized assistance.
Problem: You are using WPML 4.7.* with Automatic Translation enabled and have updated your glossary to improve the translation of key terms. After resending posts and custom post types (CPTs) for automatic retranslation, the updates were applied correctly to posts and CPTs, but existing taxonomy terms attached to those posts were not updated with the new glossary rules. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to WPML > Settings. 2. Deselect the option 'Don't show translated taxonomies in Translation Editor'. This change will allow already translated taxonomies to appear in the editor for retranslation, and they will be updated with the new glossary entries. You can then perform a small update to the default language or a bulk update and resend it for automatic translation.
Please note that this solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client imported the wrong glossary with many empty rows into their WPML site and needed either a restoration of a previous glossary or complete deletion of the current one. Solution: We advised the client to confirm they had a local backup of their glossary, as we could not restore it later. After confirmation, we proceeded to delete the glossary. We moved the issue to a forum ticket and awaited a response from our developers. The glossary was successfully deleted.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 https://wpml.org/forums/.
Problem: The client was unable to update to WPML version 4.7 and faced issues with their glossary disappearing after attempting updates and key changes in a staging environment. The glossary was not stored locally but on WPML's servers, and the client was concerned about the loss of translations and glossary entries. Solution: We advised the client to ensure they were not using the beta channel for updates and to switch to the production channel to check for updates. If necessary, the update could be manually downloaded from the WPML.org account. For the glossary issue, we confirmed that glossary entries and automatic translations are stored under an ATE (Advanced Translation Editor) account on WPML's servers, not linked to the WPML registration key. We recommended ensuring that both staging and production environments are connected to the same ATE account to avoid issues like missing glossary entries or unsynced translations. If discrepancies continue, we suggested re-registering the WPML key without affecting existing translations or glossaries, as these are managed separately through the ATE account. For detailed steps on managing glossary entries, please refer to this documentation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum.
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 you need further assistance, please open a new support ticket at WPML support forum.
