Home›Support›English Support›[Resolved] String Troubleshooting This is the list of strings that are not used or they are linked to wrong tra...
[Resolved] 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.
I’ve actually done this before. At that time, I lost the old Pay-as-you-go invoices and had to re-enter everything manually. Unfortunately, it didn’t lead to any improvement.
But if you think it’s worth trying again, I’ll do it. Or would you prefer to handle it yourself and see what happens directly? You still have the access credentials. I can re-enter the credit card details afterward if needed.
The latest error I can see is that the registration key is incorrect on the site, so I kindly ask you to register the site again, with a new registration key -and add the credit card info if necessary-. Then we can double-check if the registration key error has disappeared.
Hi,
I did this and after reconnection, the glossary is shown empty.
Then, after adding a test entry immediatley the error is shown.
Please can you check this?
Thanks, kind regards
Eric
Our 2nd-tier specialists are asking to follow these steps:
- Create a full site backup
- Deactivate all plugins, including the WPML ones
- Activate a default WordPress theme, like Twenty Twenty
- Activate the WPML plugins
- Check if the issue with the Glossary disappeared
- Activate the theme and the plugins.
Can you tell me if the issue persists in that minimal installation?
I have completed everything, but unfortunately, there has been no outcome. The site is currently in a minimal state, and development has been halted. It would be appreciated if you could take a look at the site soon, as I am waiting at this point. The login details remain unchanged. If there's anything else I can assist with, please inform me.
Thank you, best regards,
Eric
Thank you very much! Can you stay on this topic? As I mentioned before, development is currently on hold because we're waiting for the glossary issue to be fixed. Unfortunately, it's a small error, but it's crucial for the translation workflow, so it would be really helpful if the second-tier support could resolve this as soon as possible. Since the problem occurs on the main domain account and not on staging sites with a subdomain, that might be a good place to start investigating.
Thanks for your help. Could you please ask the second-tier specialist how they plan to proceed?
We need access to the site again for further development.
Hello Carlos,
what's the status — is there a solution in sight? I really need to restore my base setup and get everything running again under the main domain. I would be very grateful if this could be resolved soon so I can continue working.
I need to continue development on the main domain now, but I'm wondering what we should do: I saw that you used Duplicator — does the error also appear without the connection to the main domain? It wasn’t the case with the staging clone; the issue didn’t show up there. So my question is: can I now upload my website back to the main domain, or do your second-tier developers still need the current setup unchanged?
