This thread is resolved. Here is a description of the problem and solution.
Problem:
I have a local environment website with WPML installed. After moving the site to the server and selecting that it's a copy on localhost, I received a notice that the site moved without the option to choose it as a copy again. Attempts to reset the key by removing URLs from wp-config.php and registering a new key didn't work.
I have a local environment website with WPML installation.
The timeline of key management was as follows:
1. First I was developing locally with key for development.
2. Then I moved to the server and set the key to production mode.
3. On localhost I selected that the site was moved and the current location is only a copy and continued with further development.
4. But recently I got a notice saying: This site has moved to a new location, without the option to choose that it is a copy.
After reading many threads with solutions such as: remove site_url and home URL form wp-config.php, and reregistering the site key with a new key.
Nothing helped.
What can I do to restore the functionality of wpml plugin, please?
Thank you for contacting the support forum.
Before your ticket is assigned to one of my colleagues, please allow me to walk you through some initial debugging steps. This will help speed up the support process.
From the screenshot, I see this is the WooCommerce Multilingual tab. Please visit WPML > Translation Management there you will see the notice to move or copy.
Once you move the site to a new location you can not use the ATE on localhost. For localhost please keep it as a copy if you want to use the ATE.
The move option is for one time you can not use it again.
Hello, I am searching for the force enable ATE button, but cannot find him as mentioned in the link you provided.
Are there other methods of how to reset the key? I have an agency plan so creating additional keys to use should not be a problem but I need to preserve the translations stored in the glossary as there is almost everything translated.
sorry for my mistake as I had an older version of WPML CMS installed on localhost and misread it in the docs.
Now I see the option as in the attached picture, but I am unsure whether it is the correct thing to do in my scenario. I don't understand what it means that the sites will both use ATE (it means that both will edit the same glosary? I probably don't want that, I just want to use the old translations on localhost but not impact the translations on production server) and the sentence "Don't use this if you've moved or copied the site to a different domain on a different server" appears to me that it is my scenario.
I have a local host copy of the production site where I want to develop further and don't want to mess up translations on the production site.
Hello,
My name is Carlos and I will continue working on this site.
I understand that you desire to keep both sites (localhost and production) separated. If this is correct, then please follow these steps:
- Create a full backup of the site in localhost
- Go to WPML -> Settings -> Activate the Classic Translation Editor -> Save the changes
- Connect to the database via an Adminer plugin or PHPMyAdmin and run the following query:
select *
from wp_options
where option_name = 'WPML_SITE_ID:ate'
OR option_name = 'WPML_TM_AMS'
OR option_name = 'otgs_wpml_tm_ate_cloned_site_lock'
*this code assumes that the prefix of your database is wp_
- Delete the results
- Go to WPML -> Settings -> Activate ATE -> Save the changes
- Double-check if the issue disappeared
Could you tell me the results of the steps described above?
Please don't hesitate to contact us if you need our help in the future with WPML. We will be more than happy to help.
Best regards,
Carlos
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
