Problem: The client has translated Term Meta to Portuguese via WPML's Translation Dashboard under Yoast SEO > Term Meta, but the Term Meta of their taxonomies still appears in English in the backend, although it is correctly translated on the frontend. Solution: 1. We have identified that Yoast SEO term metas are not stored using the standard WordPress API but as a serialized option, which can lead to issues if the data becomes too large. 2. To manage translations, we recommend using the WPML Translation Dashboard to translate Yoast SEO term meta, ensuring it displays correctly on the frontend. 3. If editing is necessary, it should be done via the Advanced Translation Editor (ATE), and the term meta should be re-sent for manual translation if it was initially auto-translated. This will not incur additional credits as the translations are saved in ATE's translation memory. 4. We are considering implementing a feature where the Yoast SEO term meta field in the backend will be locked with a recommendation to use ATE for translations, to prevent issues with direct edits.
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.
Problem: The client is experiencing inconsistent capitalization in translations, specifically with the phrase 'Arame tubular para Revestimento' where 'Revestimento' is incorrectly capitalized. This issue is due to the glossary entry for 'Hardfacing' being capitalized, which overrides normal sentence-case formatting. Solution: We recommend modifying the glossary entry from:
Hardfacing → Revestimento
to a lowercase, case-insensitive version:
hardfacing → revestimento
After making this change, retranslate the affected product to ensure the correct capitalization. Additionally, clean the glossary to remove duplicates and inconsistencies to improve overall translation quality. If issues persist after these adjustments, we suggest reorganizing the glossary to ensure each term appears only once and with consistent capitalization.
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 problem continues, please open a new support ticket at WPML support forum.
Problem: The client needed clarification on how the glossary translations work in WPML, specifically whether it can handle variations of a term when the words are separated or reordered. Solution: We explained that the WPML glossary translations strictly require exact term matching. This means that the term must appear in the content exactly as it is entered in the glossary for the translation to apply. For example, if 'cored wire' is added to the glossary and translated, it will only be recognized and translated if 'cored wire' appears exactly in that order in the text. Variations where the words are separated or reordered, like 'metal cored gas shielded wire', will not trigger the glossary translation. To handle different variations, additional specific entries must be added to the glossary.
If this solution does not fully address your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Additionally, please check the related known issues and ensure you have the latest versions of themes and plugins installed. For further assistance, you can also visit our support forum.
Problem: The client reported an issue where deleted glossary terms were still being "cached" and applied in translations, despite being removed from the glossary. Solution: We advised the client to ensure that the content was not coming from a template but directly from the product content itself. After confirming that the section was indeed added via a template, the client was able to edit the relevant file and retranslate the string. This resolved the issue, and the glossary terms were applied correctly after retranslation. If you're experiencing similar issues, we recommend checking if the content is coming from a template and ensuring that all strings are sent for translation through the Translation Dashboard.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: You have a term in your glossary translating "WA HARDFACE" from English to Portuguese as "WA HARDFACE". However, when translating WooCommerce products in bulk, the term "HARDFACE" sometimes incorrectly translates to "REVESTIMENTO" instead of remaining "HARDFACE", despite being correctly translated when done individually. Solution: Our 2nd Tier Support has identified this issue and a fix will be applied server-side. Currently, there isn't anything you can do on your end to resolve this issue. We recommend waiting for the server-side update to take effect.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing an issue where the product title 'TETRA S 20 9 3-G' was not maintaining its uppercase format in automatic translations, resulting in 'TETRA s 20 9 3-g' in some languages. Solution: We resolved the issue for future translation jobs, ensuring that the original casing of product titles is maintained in translations. If you're experiencing this issue, we recommend retranslating the affected product to confirm that the case from the primary language is maintained through to the target translation.
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 for further assistance.
Problem: The client was experiencing an 'Illegal offset type in isset or empty' error when saving a WooCommerce product in a non-primary language after updating to version 4.7.6 of a plugin. Solution: We recommended updating WooCommerce Multilingual to the latest version to resolve the issue. Here are the steps we suggested: 1. Go to Plugins → Add New Plugin. 2. Click on the Commercial tab. 3. Click the "Check for updates" button. https://wpml.org/wp-content/uploads/2020/04/wpml-force-plugin-update-1.png We also advised creating a backup before updating as a precaution.
If this solution does not resolve your issue or seems irrelevant due to being 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 problem persists, please open a new support ticket at WPML support forum.
Problem: You are trying to translate a product category from English to Portuguese using WPML and DeepL. You encountered issues where specific words were not translated, phrases were duplicated, and updates to translations did not reflect changes. Solution: 1. The issue with the word 'reduced' not translating and the duplication of 'Os nossos' is due to a specific glossary combination issue with DeepL. This is a known issue and is currently being addressed by our development team. 2. We have made adjustments to how the glossary functions by removing the type of glossary, which should resolve the problem. Please check if the translation issues are resolved now.
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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that the word 'reduced' still displays in Portuguese on their product category page, even after updating the glossary and re-translating. Additionally, previously translated content does not update when re-sent for translation. Solution: If you're experiencing similar issues, we recommend you try the following steps: 1. Navigate to WPML > Settings and uncheck the option "Don't show translated taxonomies in Translation Editor". 2. Go to WPML > Translation Management, send the post with taxonomy for translation, and choose to overwrite the existing translation.
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.
