Skip Navigation

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

Problem:
The client is experiencing a recurring 'WPML detected a new address for this site' message after importing the database and performing search and replace operations during the migration of their site from a local environment to a live server.
Solution:
We recommend following the steps outlined in the WPML documentation to manage site migrations effectively. This involves ensuring that WPML settings are correctly configured to handle changes in the site URL during migrations. Please start by taking a full site backup. Then, refer to the documentation on using the Advanced Translation Editor during site moves or when using a copy of your site. You can find detailed instructions here:
Using Advanced Translation Editor when you move or use a copy of your site
Using WPML on two domains

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific case, 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 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 1 reply, has 2 voices.

Last updated by Bigul 1 year ago.

Assisted by: Bigul.

Author Posts
July 12, 2024 at 3:03 am #15939010

initiumM

Background of the issue:
We have a workflow where the main site is in examplelivesite.com. The editor changes articles and other content there. We pull the database from examplelivesite.com to a local environment, perform a search and replace to match localhost, and choose the option that the site is just a copy. After making changes locally, we push the database back to examplelivesite.com, perform another search and replace to match examplelivesite.com, and encounter the same message again.

Symptoms:
Always getting 'WPML detected a new address for this site' message after database import and search and replace operations.

Questions:
What is the recommended workflow to avoid the 'WPML detected a new address for this site' message for every database copy we make?

July 12, 2024 at 8:26 am #15940910

Bigul
WPML Supporter since 01/2013

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Welcome to the WPML support forum. I will do my best to help you to resolve the issue.

To help you faster, I've enabled debug information for this support ticket. Please see this link for how to get this information from your site and give it to us: http://wpml.org/faq/provide-debug-information-faster-support/

It happens because WPML is detecting a change in the site URL. Please note that moving your site from development to production or making a copy of your site affects your WPML site key, automatic translations, and Advanced Translation Editor features.

Therefore that is why you are getting an alert message while migrating the site. Please try the steps suggested in the following documentation after a full site backup.

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

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

--
Thanks!

Bigul