Problem: The client was experiencing an issue with a persistent warning on their staging site that said "this site has moved to a new location". Additionally, they were unable to connect the staging site to the production site for WPML translation management, as the production site would not allow them to copy a code and the staging site did not provide an option to create one.
Solution: 1. We explained that the notification appears because moving a site or creating a copy affects the WPML site key, especially when using WPML Advanced Translation Editor (ATE) features. 2. To avoid this issue when creating a staging site, we advised selecting the option *This is a copy of the original site* to use the translation memory and credits of the original site. 3. We provided documentation for further guidance:
4. We clarified that for testing purposes, we selected the option *No/You will need to assign credits or set up a pay-as-you-go plan for this site to use automatic translation* to avoid using the client's translation credits. 5. In actual use, the client should select the option *Yes (recommended)/In the next step, you will receive instructions for how to approve the credits sharing* and then use the migration code to connect with the original site's ATE credits. 6. We provided additional documentation for connecting sites:
