Glossary terms not working with punctuation

This thread is resolved. Here is a description of the problem and solution.

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.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic is split from https://wpml.org/forums/topic/split-glossary-translation-has-random-capitalization/

Tagged: ATE

This topic contains 6 replies, has 0 voices.

Last updated by rustumT 1 week, 3 days ago.

Assisted by: Kor.

Author	Posts
February 24, 2026 at 10:29 am #17845700
rustumT	Hi Kor, Unfortunately, I have been able to reproduce this issue. The Glossary terms are still being "cached" even after being deleted. - I have deleted both "Welding Alloys" and my workaround "Welding Alloys?" from the glossary and done a test retranslation, but the Glossary is still being applied. Kindly advise if the glossary "cache"/memory on my site can be cleared? Then I will be able to test this properly and provide you with a screen recording. Thanks.
February 25, 2026 at 7:35 am #17849661
Kor	Thanks for your patience. I’ve tested this on the following page: hidden link I added the glossary terms “Welding Alloys” and “Welding Alloys-pt” for the Portuguese translation. After initiating automatic translation, the glossary is applied correctly and displays as expected on this page: hidden link Could you retest this?
February 25, 2026 at 12:14 pm #17851355
rustumT	Hi, I retranslated the following product: hidden link See screen recording (There was only a change after retranslating the above product the 2nd time): hidden link* *See screenshot as well, the issue still seems to be there with the question mark: - Using the glossary: Welding Alloys > Welding Alloys-pt - Not using the glossary: Welding Alloys? > Welding Alloys?
February 25, 2026 at 3:31 pm #17852163
Kor	Thanks for your reply. I’ve checked the backend here hidden link in the Portuguese language, and I’m unable to locate the sentence “Por que escolher Welding Alloys?”. Could you please confirm if this content is coming from a template instead of the product content itself? May I also know where I can edit the entire “Por que escolher Welding Alloys?” section highlighted in the attached screenshot?
February 25, 2026 at 4:32 pm #17852425
rustumT	Hi, Yes, I confirm that entire section is added via a template. The entire section can be edited here: /public_html/wp-content/themes/enfold-child/woocommerce/content-single-product-machines.php from line 595 of that file. Please let me know if that helps.
February 25, 2026 at 5:12 pm #17852514
Kor	Thanks for your reply. This clarifies why the glossary is not being applied since the content was translated using String Translation. To ensure the glossary terms are used, please send the string for translation through the Translation Dashboard as shown in the attached screenshot. Once done, let me know the result and I will be happy to follow up if needed.
February 25, 2026 at 10:55 pm #17853155
rustumT	Thanks for explaining. I think this resolves the issue then. I have retranslated the string and this seems to be fine now. I will mark this issue as resolved.