This thread is resolved. Here is a description of the problem and solution.
Problem:
The client needed to update the WPML site key after moving their WordPress site to a new domain and server, as they were unable to access automatic translations due to insufficient tokens.
Solution:
We advised the client to generate a new WPML site key for the new domain through their WPML account, which can be done here: https://wpml.org/account/sites.
Additionally, we provided guidance on managing automatic translation credits. If the client is no longer using the old domain, they should remove the WPML key associated with it and move the credits back to their WPML account. This process is detailed in our documentation: https://wpml.org/documentation/automatic-translation/how-to-assign-automatic-translation-credits-to-your-sites/.
We also explained that automatic translation credits can be shared with different sites, as outlined here: https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, 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 the problem persists, please open a new support ticket with us for further assistance.
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 contains 3 replies, has 2 voices.
Last updated by 1 year, 1 month ago.
Assisted by: Mihai Apetrei.