Bulk translations are not using glossary term

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

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.

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.

Tagged: ATE

This topic contains 50 replies, has 0 voices.

Last updated by Kor 2 months, 1 week ago.

Assisted by: Kor.

Author	Posts
January 31, 2026 at 10:35 am #17780006
rustumT	Hi again, Can I please request a LIVE meeting/call with your 2nd tier support atyour earliest convenience? Just so we are able to share screens etc. and resolve this issue once and for all. Thanks.
January 31, 2026 at 11:01 am #17780023
Kor	Thanks for your reply and I apologize for inconvenience. Please allow me to check and I will get back to you shortly.
January 31, 2026 at 2:01 pm #17780244
Kor	Thanks for your patience. It looks like it's not getting better even after applying the solution from our 2nd Tier Support. This is what I've done previously. 1. Export the CSV file 2. Remove the terms that shows "undefined" in the CSV file 3. Go to Glossaries and delete all. 4. Reimport the newly edited CSV file. Please allow me to recheck with our 2nd Tier Support and I will come back to you as quickly as possible.
February 2, 2026 at 3:10 pm #17784484
rustumT	Hi Kor, I am still patiently waiting on feedback on this. This very critical, as it is stalling the launch of additional languages on the site. Please advise on how to resolve this issue and if there is anything else you need from me. Thanks.
February 2, 2026 at 3:12 pm #17784500
Kor	Thanks for your patience. I’ve already escalated this to our 2nd Tier Support and am currently awaiting their response. I’ll get back to you as soon as I have an update. My apologies for the delay and any inconvenience caused.
February 4, 2026 at 8:57 am #17790318
rustumT	Hi Kor, Please provide an update as a matter of urgency. The client is now quite irate due to the delay, and we need clarity on next steps. Thank you.
February 4, 2026 at 9:54 am #17790549
Kor	Thanks for your reply, and my sincere apologies for the delay. I’ve just followed up again with our 2nd Tier Support and highlighted the urgency of this issue. I’ll update you as soon as I receive their feedback.
February 9, 2026 at 6:40 am #17803753
rustumT	Hi Kor We need to provide the client an update on progress on this issue. Please provide a summary of steps taken and the way forward. Thank you.
February 9, 2026 at 7:59 am #17803945
Kor	Thanks for your patience. I've checked the report, and there are still no updates yet from our ATE team. I've just sent another message asking about the status. I will get back to you once I have feedback.
February 9, 2026 at 8:49 am #17804052
Kor	Thanks for your patience. I’ve received an update from our 2nd Tier Support team. Our ATE team is currently investigating the issue, and we should have feedback soon. In the meantime, our 2nd Tier Support team would like to review a copy of your site for further troubleshooting. With your permission, may I create a snapshot of the site? Alternatively, you’re welcome to create it yourself. For this purpose, I usually recommend the free Duplicator plugin. If you’re already familiar with Duplicator (https://wordpress.org/plugins/duplicator/), you can skip the steps below and simply share the archive file with me. You can also refer to this guide for providing a site copy: https://wpml.org/de/faq/provide-supporters-copy-site/ Please follow these steps to proceed: Watch the Duplicator instruction video: hidden link If the archive file is larger than 400 MB, use Duplicator’s file filters to exclude cache files, the wp-uploads directory, media files, and any archive files. Once the archive is ready, please share the download link with us. You may use Google Drive, Dropbox, or a similar file-sharing service, as the snapshot file can be quite large.
February 9, 2026 at 10:04 am #17804344
rustumT	Great. Still waiting patiently to get this resolved ASAP. So, please go ahead and create a snapshot on your side. Please let me know if there is anything additional you need to help see this through to completion. Thanks.
February 9, 2026 at 1:58 pm #17805336
Kor	Thanks for your reply. I've created a package and forwarded it to our 2nd Tier Support. I will come back to you once I've feedback.
February 11, 2026 at 6:32 am #17811441
rustumT	Good Day Kor, We have not yet received any further update from the team on this matter. Please advise on the current status as a priority. If progress remains limited, we request that a meeting be arranged with your second-level support team as soon as possible to expedite resolution and avoid any further delays. Thank you
February 11, 2026 at 6:46 am #17811445
Kor	Thanks for your reply. Our 2nd Tier Support team has escalated this to our ATE developers, and they are currently investigating the issue. I will get back to you as soon as I receive an update. My apologies for the delay and any inconvenience caused.
February 12, 2026 at 9:59 am #17815831
Kor	Thanks for your reply. This is fixed and could you please check? Our 2nd Tier Support corrected this on our server side.