This thread is resolved. Here is a description of the problem and solution.
Problem:
The client is experiencing an issue where a blueprint of a previous website was used to replicate a site in Local, resulting in WPML database settings from the original site (anum.eu) persisting in the new site (vilandert.local). An error message indicates that the site has moved to a new location, and translations are not appearing correctly.
Solution:
1. Check the
wp-config.php
file for any code that defines the site and home URL. If found, remove it and set up the site URL in the WordPress admin area under Settings > General. For more details, refer to our documentation: https://wpml.org/errata/persistent-warning-this-site-has-moved-to-a-new-location/.
2. If the issue persists, follow these steps:
- Backup your database and website.
- Access your database and run the following query:
SELECT *<br />FROM wp_options<br />WHERE option_name = 'WPML_SITE_ID:ate'<br />OR option_name = 'WPML_TM_AMS'<br />OR option_name = 'otgs_wpml_tm_ate_cloned_site_lock'
Replace "wp_" with your database prefix.
- Delete the entries found by the query.
- Navigate to WPML > Settings in the admin area, select the Advanced Translation Editor (ATE), save the settings, and wait for ATE to activate.
If this solution does not seem relevant to your issue, please open a new support ticket at our 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.
This topic is split from https://wpml.org/forums/topic/i-get-the-message-wpml-plugin-cannot-connect-to-wpml/
This topic contains 1 reply, has 2 voices.
Last updated by 1 year, 1 month ago.
Assisted by: Long Nguyen.