Problem: The client experienced issues with the WPML plugin after migrating their WordPress site to a new domain. The main problem was that the AMS servers retained a stale site fingerprint even after the site was deleted from the account dashboard, causing a loop that prevented the use of migration credits. Solution: 1. The client deleted all sites associated with their account through the WPML.org dashboard. 2. They ran targeted SQL queries against the WordPress database to remove license and registration data while preserving all WPML configuration, settings, and translations. This action prompted the plugin to register as a new site. 3. Upon encountering a recurring issue with the site migration message, the client found and deleted the
otgs_wpml_tm_ate_cloned_site_lock
option in the database, which contained a stale fingerprint. However, this did not resolve the issue as the AMS server recreated it with the same stale fingerprint. 4. The client eventually chose the non-recommended option in the migration wizard, re-entered the site key, and successfully registered the site.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
