[Resolved] Glossary Tool did not work. How can I fix the situation now on.
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with the WPML glossary feature not being taken into account during automatic translations. They are looking for a way to update the glossary and retranslate pages efficiently, as well as inquiring about slug translations and the possibility of recovering credits due to the initial failure.
Solution: 1. We recommend updating the glossary entries by going to WPML > Translation Management > Tools tab > Glossary. Here, you can edit the item and change the type to Name, or create a new item with the type Name and delete the current one. 2. After updating the glossary, return to the Translation Management tab, select the pages in bulk, and send them to automatic translation. 3. We suggest testing with 1-2 pages first to ensure the glossary is working correctly. If issues persist, please provide screenshots of the problem. 4. Regarding slug translations, the glossary will apply if you translate the page slug in the Advanced Translation Editor. To enable slug translation, navigate to WPML > Settings > Translated documents options > Page URL and select Translate.
Tell us what you are trying to do?
I created a glossary of terms before automatically translating into different languages but it has not worked in any case. It has been translated without taking the glossary into account.
Now, I need to change the terms on each page and in each language and I am looking for a way to speed up the process at least...
Thank you for contacting WPML support, I'd be happy to help you with this issue.
Can you please share some screenshots of the issue with the glossary and translation on your site? You can try to use the glossary type "Name or Proper Noun" and check this issue again.
Hi, I have hidden the languages that have not been translated correctly so they have also been hidden from the Glossary. I can't pass you the Screen you are asking for.
I would like to know if there is a way to update the Glossary and automatically re-translate the pages that have already been translated taking into account this glossary.
In case it is better to delete all the wrong translations and redo the process, could you help me? could you give me back the credits to do it again?
I'm afraid that the credits aren't refundable as we pay the translation engines for those translations, and can't be reverted.
You can update the Glossary and send the pages to automatic translation from WPML > Translation Management or manually edit each page and use the automatic translation feature in the Advanced Translation Editor to translate only some sentences there.
Please check this screenshot hidden link
I hope they are, this have been a WPML bug, not my fault.
One of the things made me trust WMPL was the Glossary feature, and it did not work.
We can not translate page by page becuase that takes too much time. We are preparing our web for 10 languages and we use technical terms that need to be translate automatically with the Glossary...
Can you send me a Setp by Step to update the glossary and send all the URLs to translation?
One more question, do the slug translation take into account the glossary?
You can follow steps below to translate the page again:
1. Go to WPML > Translation Management > Tools tab > Glossary > Edit the item and change the type to Name, or create a new item with the type Name and delete the current one.
2. Go back to the Translation Management tab > Select the pages in bulk and send them to automatic translation. Please check the screenshots attached.
I suggest you test with 1-2 pages and see if the Glossary works correctly on your site. If not, please share some screenshots of the issue, I will try to replicate the issue on my site.
Regarding the slug, the glossary is applied to the slug also if you translate the page slug in Advanced Translation Editor. You can go to WPML > Settings > Translated documents options > Page URL > Select "Translate" to translate the page slug.
Hi, thanks I have just tried this way and it is working better.
However, the first time it didn't work and it has consumed us more than 100.000 credits...
I would like to know if there is any way to open a claim to recover them, as it has also meant a delay in our work, SEO problems and more hours invested...
