This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with WPML where it frequently requires reconfiguration. The dashboard displays an error indicating that the site key is incorrect and that the REST API is disabled, although it is not. Attempts to resolve the issue by generating a new site key and re-registering have been unsuccessful. Solution: 1. Verify if the issue persists without activating the WPML license. You might be able to complete the configuration without activating the license. 2. Deactivate and delete the current version of WPML, then reinstall the latest version from https://wpml.org/downloads/. 3. Check the wp_options table in your database as the WPML configuration settings are stored there. It's possible that these settings are being removed or wiped clean, necessitating repeated reconfigurations. 4. Ensure you have a full backup of your database and website before proceeding with any changes. We recommend using the Duplicator plugin, available at http://wordpress.org/plugins/duplicator/.
If these steps do not resolve your issue, or if the solution provided here becomes outdated or does not apply to your specific case, 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 problems persist, please open a new support ticket at WPML support forum.
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.
Background of the issue:
I'm not sure why our instance of WPML keeps breaking. It seems that the configuration is breaking somehow. Things will be fine one second and then we get an error in our dashboard saying that the site key is incorrect and the entire plugin will need to be reconfigured. WPML is saying that our rest api is disabled but it's not. I've tried adding a new site key but that doesn't seem to work.
Symptoms:
Error in dashboard saying that the site key is incorrect and WPML needs to be reconfigured. WPML is indicating that the REST API is disabled.
Questions:
Why does our instance of WPML keep breaking?
Why do we get an error saying the site key is incorrect?
Why does WPML indicate that the REST API is disabled when it's not?
How can we resolve the issue of needing to reconfigure WPML repeatedly?
I've tried adding a new site key following these steps but it doesn't help:
- Go to your account page (https://wpml.org/account/sites/)
- Delete the key for the site - hidden link
- Go to Plugins>>Add New>>Commercial tab
- Click on \"Unregister WPML from this site\"
- Refresh the page
- Click on \"Get a key for this site\"
- Copy the newly generated code
- Visit back to Plugins>>Add New>>Commercial tab
- Register the site with the new key
I am glad the Rest API issue is resolved. Regarding the license issue, if you proceed without activating your license do you still experience the issue of WPML asking you to reconfigure it again?
You should be able to finish the configuration without activating the license.
Also, if possible, deactivate and delete the current version of WPML and re-install the latest version from here https://wpml.org/downloads/
Hi Bobby, I've actually reverted that rest api workaround because it didn't actually resolve our issue. I'm not seeing an option to add/activate a license. Under the WPML tab there's only "Setup" and "Support" and going to setup takes me through the entire config process. The problem there is I'm not sure what the original configuration was. I'm not really clear what is causing this issue either. If we revert the site back to a previous version that worked fine and wait long enough this issue reappears. We don't have this plugin autoupdating so I'm not sure what could be triggering this.
Also, installing the latest version is presenting an issue because there is an issue where activating newer versions of the plugin almost doubles the average transaction time on our server. We have a manual workaround that you guys provided that was added by the previous developer and if we update then that will need to be either re-applied or re-architected.
The WPML config is saved within the database's wp_options table.
There is a possibility something is triggering this entry to be either removed or wiped clean, meaning that each time you would need to set WPML up again, even though the translations remain intact.
Please share with me the site's default language and its secondary languages.
I would like to request temporary access (wp-admin and FTP) to your site to test the issue.
(preferably to a test site where the problem has been replicated if possible)
**Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken **
I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/
You will find the needed fields for this below the comment area when you log in to leave your next reply.
The information you enter is private which means only you and I have access to it.
NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin.
Thanks Bobby, we got this sorted out. It turned out to be a WPEngine process that strips any db tables/rows over a certain size limit and the icl_sitepress_settings is huge because it stores all of the wpml options. What's the likelihood that you guys can refactor that so that it doesn't get so big?
