Problem:
Issues with WPML key registration in migrations between staging and production environments.
I am trying to push changes from the staging to the dev environment (to update the site's content in this environment) and from staging (to prod to publish new tested content).
However, I got this message every time we push the changes from staging to prod:
“This site has moved to a new location
You or someone else moved this site to https://staging.my-domain.com. Please keep in mind that:
Translations that you do at https://staging.my-domain.com will not appear on this site.
You cannot edit translations on this site.
The site at https://staging.my-domain.com is using the same credits for automatic translation as this site.
If you didn't intend to move this site to https://staging.my-domain.com, you can indicate that this site should be at https://dev.my-domain.com.”
Solution:
To fix it please follow these steps:-
1. Make sure you have a complete DB backup of site.
2. Run this query on the database:
select *
from wp_options
where option_name = 'WPML_SITE_ID:ate'
OR option_name = 'WPML_TM_AMS'
OR option_name = 'otgs_wpml_tm_ate_cloned_site_lock'
replace "wp_options" with the correct table name.
3. Delete those entries.
4. Go to WPML > Settings and select use the advanced translation Editor + save and wait for ATE to get activated.
5. Use this guide to link production and staging if needed:
https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/
Also, next time If possible, you can preserve the values of "WPML_SITE_ID:ate", "WPML_TM_AMS", "otgs_wpml_tm_ate_cloned_site_lock" in the wp_options table. These are three option keys that trigger the notice.
Note that you must do it before WPML request to the server i.e. change the value even before you load the site after DB restoration.
We are still working on both issues, and I hope it will be improved in future versions.
