Skip Navigation

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.

Sun Mon Tue Wed Thu Fri Sat
- 12:00 – 16:00 10:00 – 14:00 10:00 – 14:00 9:00 – 13:00 9:00 – 13:00 -
- 17:00 – 21:00 15:00 – 19:00 15:00 – 19:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Europe/Bucharest (GMT+03:00)

Tagged: 

This topic contains 3 replies, has 2 voices.

Last updated by Mihai Apetrei 1 year, 8 months ago.

Assisted by: Mihai Apetrei.

Author Posts
July 17, 2023 at 8:45 am #14047437

ondrejF

Hi!

I copied a production website to staging, and I started seeing the WPML alert saying "This site has moved to a new location" with some confusing information - see the screenshot.

I believe I should have gotten an alert saying "WPML detected a new address for this site" instead.

I went ahead and changed the site WPML key to a development key matching the staging URL.

But the same alert is still there, so I can't translate on staging.

Can you please help?

Screenshot 2023-07-17 at 10.38.07.png
July 18, 2023 at 8:35 pm #14062025

Mihai Apetrei
WPML Supporter since 03/2018

Languages: English (English )

Timezone: Europe/Bucharest (GMT+03:00)

Hi there.

WPML is able to see that the site is existing on a production environment due to the key and it tells us practically that the live site is at that URL, so this current site is a copy of that.

Some related documentation:
https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/using-advanced-translation-editor-when-you-move-or-use-a-copy-of-your-site/

Can you also please let me know if there's anything showing up in the live site?

If it is, select on the production: NO, I changed the address of the site to this new one

Please let me know.

Mihai Apetrei

July 19, 2023 at 12:25 pm #14066039

ondrejF

I am sorry, I still need help. I've read the documentation and it looks like the detection got it backwards.

The site runs on tratson.ch and there are no issues and no alert.

I've cloned the site to staging url, and on the staging url it says that the site has been moved to tratson.ch.

So I click on "indicate that this site should be at hidden link" and then click "No - keep the site on hidden link".

But that simply takes me back to the alert.

I've generated a new development key for the staging site and updated the key within WPML, but the alert is still there and I can't translate on staging.

August 8, 2023 at 1:24 pm #14169523

Mihai Apetrei
WPML Supporter since 03/2018

Languages: English (English )

Timezone: Europe/Bucharest (GMT+03:00)

Thank you for the updates.

After a lot of digging, I'm coming back with more questions.

There are multiple reasons that can cause this notification to continue to pop up so I will still have to ask some questions (hopefully that will be fine with you) so that I can better understand what exactly was done before seeing the notification.

We have:

1. Tratson
2. Tratson dev

You said that the site was copied/migrated from PROD to DEV.

But here's something important that I need to understand because I think this might have happened:

1. you guys had the live tratson and (possibly or not) the dev environment
2. you might have created the dev version after the live one or maybe dev was first
3. you worked on the dev version
4. then you moved it to prod
5. in prod you saw the migration banner
6. in prod then you selected the "MOVED" version
7. However, now you might have returned to the staging site or maybe you activated the staging site again

From that notice, seeing that still, means that the staging site is still not migrated FROM the main site so it shows this banner on staging.

So I would need to know the whole complete process that took place with these 2 environments so that I can hopefully better understand what happened and how we can fix it.

Please let me know.

Mihai

The topic ‘[Closed] Website copied to staging, wrong URL change detection by WPML’ is closed to new replies.