Home›Support›English Support›[Resolved] Site's "New Location" is exactly the same as it's previous location
[Resolved] Site's "New Location" is exactly the same as it's previous location
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with WPML prompts after moving their site from a staging to a live environment, despite using the same site key for both environments.
Solution: We recommend the following steps to resolve the issue: 1. Go to WPML → Support in your WordPress dashboard. 2. Click on the Troubleshooting link. 3. On the WPML Troubleshooting page, click the button labeled 'Force-enable WPML’s Advanced Translation Editor'. 4. You can now use WPML’s Advanced Translation Editor to add, edit, and manage translations on both domains without seeing the migration wizard.
Please note that this solution might be irrelevant if it’s outdated or not applicable to your case. If the issue persists, 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 necessary, please open a new support ticket 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.
You will recall that we created and registered site keys for BOTH my LIVE site as well as my staging site.
Since we last spoke, I have done the following:
(1) Cloned/Pushed the LIVE version of our site to the Staging Environment.
Seeing as (A) there is no avoiding overwriting the site keys when moving the site from one environment to another in Kinsta's hosting and (B) we seemed to agree that it would be fine to use all translation credits in our LIVE environment, I didn't bother updating the site key in the staging environment (letting it remain the same key as the LIVE environment). I just ignored any prompts from WPML in my WordPress dashboard while making a few updates to my site. I made no updates to WPML in the staging environment and have no intention of doing so in the future either.
Once finished with making the desired changes to my staging site, I pushed those changes to my LIVE site this morning:
When I logged into my LIVE site, I received the following prompt from WPML. (see attached image)
I am confused why I am seeing this as it's the exact same URL, containing the exact same site key.
I'm not sure what I should do now seeing as my goal is to use WPML on my LIVE site (and ignore it when making changes to other aspects of my site (in the staging environment).
I need a workable, repeatable process that doesn't break anything.
This issue is not related to licence keys, as licence key and ATE / automatic translation are not really directly related. So licence key is used for WPML to work correctly and enable ATE, but when you move your website from staging to dev, WPML also needs to migrate data related to your automatic translation account (memory, credits, ID and etc), this is what for banner is.
Sometimes this can go wrong and cause issue as you are experienced, can you please follow next steps from our docs:
However, if both domains point to the same website on the same server, you should not use the migration wizard. Instead, follow these steps:
- From either your primary or secondary domain, go to WPML → Support and click on the Troubleshooting link.
- On the WPML Troubleshooting page, click the button labeled Force-enable WPML’s Advanced Translation Editor.
- Now, you can use WPML’s Advanced Translation Editor to add, edit, and manage translations on both domains. You should also not see the migration wizard anymore.
