String Troubleshooting This is the list of strings that are not used or they are linked to wrong tra...

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

Problem:
You are working on a site under development and managing a large database caused by WPML. You have a glossary that is not functioning correctly, which works on a staging site but has issues in the production environment. The main symptoms include a huge list of strings that are either not used or linked to the wrong translation data, and the glossary itself has an error preventing its use.
Solution:
We discovered that the English language was mapped under an incorrect language code on our servers. We corrected this mapping for your site, which resolved the glossary error. It's possible that this issue was due to human error or a technical exception.

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 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.

Tagged: ATE, Exception

This topic contains 40 replies, has 2 voices.

Last updated by Carlos Rojas 2 months ago.

Assisted by: Carlos Rojas.

Author	Posts
June 5, 2025 at 1:06 pm #17110355
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi Eric, You can restore a copy of the site, and if the issue disappears, continue working while our 2nd tier specialists investigate the cause of the issue on their side.
June 5, 2025 at 6:58 pm #17111732
ericH-23	Hi Carlos, Thanks, but I already reinstalled a copy once before — without success. The error was still there. But can I now go ahead and install it again, most likely with the error still present, and continue development? Once a solution is found, my site can then be improved accordingly. Is that correct? Thanks and best regards, Eric
June 6, 2025 at 6:16 am #17112869
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Yes, correct.
June 12, 2025 at 11:02 am #17129672
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi, Our 2nd tier specialists copied the glossary terms to the production site. Please double-check if the issue has disappeared.
June 12, 2025 at 11:39 am #17129836
ericH-23	Hi Carlos, Thanks for your message. I’ve checked the production site, but the issue is still there. How exactly was something copied — without backend access (which is still deactivated for wpml user)? Was it copied in the WPML cloud to the production domain? What should I do next? Thanks and best regards, Eric
June 12, 2025 at 12:06 pm #17129985
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi Eric, Yes, the glossary entries on our servers were copied from the staging site to the production site. Can you share the access credentials to the production site again so our 2nd-tier specialists who copied the glossary terms can double-check the configuration? I have set your next message private.
June 12, 2025 at 1:05 pm #17130230
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi Eric, Thank you very much. I just updated our 2nd tier specialists with the credentials so the can compare the behavior in the production with the information in the server side.
June 13, 2025 at 7:54 am #17132002
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi Eric, Our 2nd-tier specialists identified the cause of the issue as incorrect language mapping and corrected it. Now you can see the glossary terms on the production site. Can you confirm that the issue was solved?
June 13, 2025 at 8:32 am #17132145
ericH-23	Hi Carlos, Yes, the issue appears to be solved — I can now see the glossary terms on the production site, thank you! However, I’d kindly ask you to explain in more detail what exactly was wrong and what was corrected — specifically where and how the language mapping was fixed. This would help me better understand the issue and avoid similar problems in the future. Thanks again for your support — much appreciated! Kind regards, Eric
June 13, 2025 at 8:52 am #17132318
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi Eric, I'm happy to hear that the issue is solved. Our specialists found that the English language was mapped under an incorrect language code on our servers (the English language from your site). They fixed the language code on our servers for your site, and that was it. I can't say for sure why the English language was incorrectly mapped. Perhaps it was a human error or a technical exception.
June 13, 2025 at 9:31 am #17132474
ericH-23	Hi Carlos, Thanks! It's strange though that the issue didn't occur on the staging site – it seems it was already corrected there. But good to know what the problem was. Thanks again for the help – much appreciated! Best regards, Eric
June 13, 2025 at 9:38 am #17132683
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi Eric, Please don't hesitate to contact us if you need our help in the future with WPML. We are here to help 🙂 Have an excellent day!