Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client installed WPML CMS on a staging site and migrated it to a live site, resulting in a WPML alert about the URL change. The client was unsure about the correct steps in the migration wizard, specifically whether to start with 'Yes' or 'No' and how to handle the site key registration and unregistering process.
Solution:
1. In the WPML > Translation Management, select "Yes/This is only a copy - original site is still running" for the first prompt.
2. For the second prompt, choose "No/You will need to assign credits or set up a pay-as-you-go plan for this site to use automatic translation".
3. Continue using the staging site's WPML site key for translations until you are ready to deploy to the live site.
4. Upon deploying the staging to the live site, expect a "site key mismatch" warning. Then, perform the following steps:
- Log in to WPML.org > My Account > Register WPML on your sites
- Delete the staging site key if no longer in use.
- On the live site, navigate to WP > Plugins > Add new > Commercial Tab.
- Click "Unregister WPML from this site" and then "Register WPML" again using the production site key.
This process ensures the live site is correctly registered with WPML, and future translations will utilize the correct site key.

If this solution does not resolve your issue or seems outdated, we 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 further assistance is needed, 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.

Tagged: 

This topic contains 6 replies, has 1 voice.

Last updated by dominicC-10 1 week, 4 days ago.

Assisted by: Kor.

Author Posts
July 16, 2025 at 7:00 pm #17243451

dominicC-10

Background of the issue:
I installed WPML CMS at a staging site (hidden link) to implement translations into French, Spanish, and Portuguese. These translations are complete, but I still need to implement translations into simplified and traditional Chinese on the staging site. I have deployed the staging site to the live site (hidden link) and noticed a WPML alert about the URL change. I believe I need WPML CMS running on both the live and staging sites to complete the Chinese translations and then push them to the live site.

Symptoms:
I see a WPML alert on the live site dashboard about the URL change.

Questions:
Can you confirm which steps I should take in the migration wizard?
What is the process for site key register/unregister?

July 16, 2025 at 7:07 pm #17243553

dominicC-10

I've also been reading https://wpml.org/faq/how-to-remove-the-this-site-is-registered-on-wpml-org-as-a-development-site-notice/

But not sure whether I should do this first, or if it is done as ppart of the migration wizard.

My confusion lies in that I AM moving the site to a New url, so according to https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/using-advanced-translation-editor-when-you-move-or-use-a-copy-of-your-site/ I should select 'NO' as the initial wizard step. But really the live site is a copy of the staging site, so I think I want to 'Copy site with migration code' possibly. Which means starting the wizard with Yes.

I don't imagine I will be doing actual translations on the live site, until I have finished the Chinese translations on the staging site and had these approved. After this I will then deploy the full staging site to the live site again.

July 18, 2025 at 1:39 am #17248399

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for contacting us. Please select "Yes/This is only a copy - original site is still running" for the first prompt in WPML > Translation Management.

Then, when you get the second prompt, you can select "No/You will need to assign credits or set up a pay-as-you-go plan for this site to use automatic translation"

July 28, 2025 at 1:58 pm #17275636

dominicC-10

Thanks for clearing that query up Kor.

I've followed your instructions. This results in me seeing hidden link

I may indeed implement the suggestion at https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/

I have also tried to follow the instructions at https://wpml.org/faq/how-to-remove-the-this-site-is-registered-on-wpml-org-as-a-development-site-notice/ and this results in me seeing hidden link

When I follow the 'where to insert key' link I'm taken to https://wpml.org/faq/install-wpml/#register (???)

And when I go to 'Add new plugin' I see hidden link

This is a grab of the communication error screen - hidden link

What should I do now?

July 28, 2025 at 2:02 pm #17275640

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. The option to input the sitekey is in WP > Plugins > Add new > Commercial Tab . I've attached a screenshot for your reference.

Screenshot_266.png
July 28, 2025 at 2:10 pm #17275670

dominicC-10

Kor

Thanks for speedy reply

I've now assigned the new production key to the live production site, the banner has gone and the comms error has gone too, so all looks good.

What will be my WPML site key process in a few days, assuming the following:
– Translations for chinese x 2 are executed on the staging site
– Once approved, staging site is fully deployed to overwrite the live production site
– No further translation works done on staging & all future translations to be executed on the live/production site (staging site will probably be deleted).

Appreciate you wrapping this up for me.

July 28, 2025 at 2:15 pm #17275711

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. Based on your described workflow, here's what will happen with your WPML site key and what you should expect:

1. Translations on Staging Site:
You can continue using the staging site's WPML sitekey for translation work. Since this is temporary, it's fine to keep the staging key active until deployment.

2. Deploying Staging to Production:
Once you overwrite the live site with the staging version, WPML may temporarily show a "site key mismatch" warning. This is expected because the new site’s database includes the staging key.

3. What You Need to Do After Deployment:

-Log in to WPML.org > My Account > Register WPML on your sites

-Delete the staging site key if you're no longer using it.

-On your live site, go to WP > Plugins > Add new > Commercial Tab

-Click "Unregister WPML from this site"

-Then "Register WPML" again using the production sitekey

This ensures the correct key is tied to your live site moving forward.

4. Future Translations:
Since all future translations will be done on the live site, no further action is needed after the re-registration. You’ll be set up with the correct key and translation memory will carry over if you’re using the Advanced Translation Editor.

July 29, 2025 at 8:56 am #17277772

dominicC-10

Many thanks Kor, that will be very useful to refer back to.