String translations are currently not working on site ID 1 for our client Bunk. They only work when (Auto register strings for translation) is activated OR the site is another site ID for example:
1. hidden link Does not work
2. hidden link Does work
Thanks for contacting WPML forums support. I'll be glad to help you today.
Could you please try the following steps?
1- Go wp-content folder on the problematic site
2- Rename the languages folder to "languages.old"
3- In your dashboard, go to WPML-> Support-> Troubleshooting
4- Click on the "Show custom MO Files Pre-generation dialog box"
5- Go to String Translation and translate any string
6- Clear the cache and check the front end
❌ Please backup your database and website ❌
Kindly let me know if the above steps helped you fix the issue.
Thank you for your prompt reply. We've tried doing this and unfortunately there is no change. In face all the string translations were all already set within the string translation editor even after regenerating the languages folder data as instructed.
Let me know what our next steps are as this issue is preventing this site from going live.
Thanks for your update. Could you please give me an example of the problematic strings to check them?
Also, I would need to look closely at your site, so I would need to request temporary access (WP-Admin and FTP)
– preferably to a test site where the problem has been replicated if possible –
in order to be of better help and check if some configurations might need to be changed.
Your next answer will be private, which means only you and I can access it.
❌ Please backup your database and website ❌
✙ I would need your permission to de-activate and re-activate the Plugins and the Theme and change configurations on the site. This is also a reason the backup is critical.
✙ I also need your permission to take a local copy of your site to debug the issue without affecting your live site.
We've been trying to fix this on our side and have come across something interesting. The problem seems to have been resolved. However, we haven't needed to do this for our other sites with the same setup.
Adding the domain to this list in Theme and plugins localization did the tirck
1) These settings are disabled on Amsterdam and Utrecht and yet they work
2) Doesn't seem the most futureproof solution if someone decides to define a new domain
