This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with WPML where translations are not appearing or are lost after making changes. This occurs even after using an older recommended version of WPML.
Solution: We recommend the following steps to potentially resolve the issue: 1. Update WPML to the latest version (4.7) and String Translation to 3.3.0. Follow these detailed steps: - Navigate to Plugins -> Add New -> Commercial. - Unregister WPML by clicking the unregister link. - Visit https://wpml.org/account/sites/ and delete the existing site key. - Create a new site key for your site. - Return to Plugins -> Add New -> Commercial on your website. - Click the register link and use the new site key to register. - Click "Check for updates" button to list new versions. 2. After updating, clear all caches and retry accessing the privacy page or any other page. Please ensure to take a full backup of your website and database before proceeding with these steps.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 problems persist, 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.
Ok fine. I will transfer a current version as soon as possible and test there too. This probably won't be for today or tomorrow. Is it possible to put this onhold for a few days?
Thanks!
Additionally, when you check again on staging, can you please also tell if you previously migrated the sites between the 24th and 27th of January by any chance? If you did, do you remember the exact date?
No urgency, just let me know along the previous one, when you're ready, thanks.
I installed a full up-to-date image of the live website on the staging site. Today I wanted to make another small adjustment to the privacy statement page. It was 100% at first, but as soon as I added an extra line in the first paragraph, the translation came up at 54%. Not only the paragraph where I wanted to add the text had to be re-translated, texts further down the page (where I didn't change anything) also had to be re-translated. I then fully translated the page back and saved it that way. After this adjustment, the translation remained at 100% when I removed (as a check) the extra text again. But as soon as I changed something in another place, I had to translate the whole section again. Presumably because I set “I prefer bigger segments” for that page too. I had already set this on the other pages and apparently it is not taken over on other pages. So I had to translate it a second time. At this moment everything remains at 100%.
Unfortunately I have not been able to make a screen recording of this.
May I ask if you can check the pages on the staging site to see if everything is okay now? If my client makes a small change and then she has to translate everything again, she is going to pass this on to me anyway. Which again will cost me a lot of time.
Thank you for your patience and cooperation. I checked randomly different pages but didn't make any change, however, I noted that the setting for "I prefer bigger segments" remains intact, which I turned off (see attached).
One thing I noted with the privacy page is, that I added new lines which were present in the ATE. I translated these, added more lines and repeated the process. All changes remained well. But one segment still losing the translation.
I suspect this is the same case as it was with "Wie is Ellen?" page and perhaps it may be lurking in other pages. My apologies I couldn't check each page because it is a very cumbersome process.
However, I'll circle back to my previous questions (by our team):
- Did you previously migrated the sites between the 24th and 27th of January by any chance? Or any idea around when you did the last migration (except the one you just refreshed the staging a few days ago)? This is about migration like developed on staging and then migrated to production.
- Is this same issue happening on the Live site?
- Can you update WPML to latest 4.7 and String Translation to 3.3.0? But do not just update by uploading new version, which I can do myself. BUT, try the following steps:
--- In your staging, go to Plugins -> Add New -> Commercial.
--- Unregister WPML by clicking the unregister link.
--- Then go to https://wpml.org/account/sites/.
--- Delete the existing site key for this staging site.
--- Create a new site key for this staging site.
--- Then go back to Plugins -> Add New -> Commercial on your website.
--- Click the register link and use the new sitekey (created above) to register.
--- Then click "Check for updates" button, so it lists new versions in the table below this button.
- Update WPML and String Translation to new versions.
- Clear all caches and retry that privacy page or any other page.
I will provide you with all the answers to the questions asked today. This will be in the late afternoon.
One important question though. I am currently starting translations on a new website. There I have just installed the latest version of WPML 4.7 and 3.3. Should I also select “Use the previous version of the Advanced Translation Editor” there? Or can I just use the new one? Also, is it safe to leave “I prefer bigger segments” on this time? Hopefully I won't have any problems with this new website!
Yes for the new site, please continue using the new interface, as well as, the way you want it (i.e. bigger segments or not) and feel free to report any issue in separate ticket. So our support can investigate accordingly, instead of mixing different setups.
P.S.: I'll be off over the weekend and 'll be able to attend on Monday.
The website was developed at the final production site from the beginning. No migration happened. During the development of the website, I protected it with an “under construction” plugin (seedprod). That way I could quietly continue development and visitors would just see a “coming soon” page. I just created an image and transferred it to a staging site at your request to see the problems. In January, I restored 2 images. One on Jan. 12 and a second on Jan. 17. The last one was on February 10.
I performed the procedure as you described and afterwards added an extra line in the privacy page and the translation worked.
The segment that kept losing translation with you translated perfectly this time. as an extra test I put a new line just below the segment and afterwards also put an extra line within the segment itself. Both additions tested separately and each time with a perfect translation.
As I see it now, there was no more problem translating that page.
I did notice that in the settings the “Use the previous version of the Advanced Translation Editor” is disabled and I am using the new ATE. I assume that I can use the new version again?
Is it safe to perform this procedure on the live website as well? Or do I need to take other steps first?
Thank you for the updates and glad that it worked on the staging.
If you're referring to the same steps as I mentioned in my previous message, like below:
- Update WPML to latest 4.7 and String Translation to 3.3.0. But do not just update by uploading new version. While, try the following steps:
--- Go to Plugins -> Add New -> Commercial.
--- Unregister WPML by clicking the unregister link.
--- Then go to https://wpml.org/account/sites/.
--- Delete the existing site key for this site.
--- Create a new site key for this site.
--- Then go back to Plugins -> Add New -> Commercial on your website.
--- Click the register link and use the new sitekey (created above) to register.
--- Then click "Check for updates" button, so it lists new versions in the table below this button.
- Update WPML and String Translation to new versions.
- Clear all caches and retry that privacy page or any other page.
Sure you can try these, however, please take full backup of your website and database beforehand.
