This thread is resolved. Here is a description of the problem and solution.
Problem:
The client is unable to add a new plugin on the production website to register a new WPML API key after deleting the old one. The website crashes when trying to remove restrictions for adding new plugins. The client also inquires about changing the API key directly in the database and retrieving a deleted API key.
Solution:
If you're experiencing issues with your WPML API key after migration and are unable to register a new one due to restrictions, we recommend clearing all local and server caching, which might be causing the issue. If you need assistance with server caching, contact your hosting support.
To add a new WPML key directly, you can insert it into your
wp-config.php
file. Detailed instructions are available in our documentation:
Automatic WPML Registration using PHP
Unfortunately, once a WPML key is deleted, it cannot be recovered. However, you can generate a new one, which will be automatically created.
Changing the API key in the database is possible but not recommended due to its complexity. If you still wish to proceed, you can follow the steps provided by another user in this forum post:
Change API key in the database
For site migrations, we suggest using the Duplicator plugin, which ensures a proper migration process. You can find the plugin and documentation here:
If this solution doesn't seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
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 1 reply, has 2 voices.
Last updated by 1 year, 7 months ago.
Assisted by: Mihai Apetrei.