Problem: The client needed to know how to change their site from a development domain to a production domain in WPML after moving their site to a new domain.
Solution: 1. We recommended using the Duplicator plugin to migrate the site and handle the URL-replacing process. Documentation for Duplicator can be found at https://snapcreek.com/duplicator/docs/ and a tutorial at https://www.youtube.com/watch?v=3YDQ3Ey_2wY. 2. After migration, the client should unregister WPML from the old domain and register it for the new domain. This involves logging into the WPML account, removing the old site, adding the new site, and using the new key provided in Plugins > Add new > Commercial. 3. If the option to update the site key is not available, the client should click "Unregister WPML from this site" and then re-register with the new key. 4. For the issue with the old domain name still appearing in the "Theme and plugins localization" section, we advised that nothing should break if the client changes it to the new domain, but recommended using a plugin like Duplicator to ensure all URLs are correctly replaced.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 needed, please open a new support ticket at our support forum.
Simple Download Monitor plugin - the link in the translation is not working
Solution:
The user had our Blog subscription, a limited version without Strings Translation. The Simple Download Monitor plugin Is not officially compatible with WPML. So it might be a problem.
It is worthwhile to try to preserve the URL arguments. You can read about preserving URL arguments here.
Problem: The client is unable to update the WPML site key on a cloned development site and is receiving an alert stating "WPML plugin cannot connect to wpml.org".
Solution: 1. Unregister the old WPML key by navigating to the WordPress backend, then go to Plugins > Add New > Commercial. 2. Register with the new WPML key in the same location. 3. To address the connection alert, it may be a false-positive due to server caching. To verify, click the "check for updates" button in the Plugins > Add New > Commercial section. If the page refreshes and WPML still shows as registered, the alert is indeed a false positive and should clear when the cache refreshes.
