Problem: The client was experiencing issues with the WPML sitekey on their staging site, which was set up as a copy of the production site. They were unable to use the same sitekey for both environments due to their deployment process, which overwrites the production database with the staging database. Solution: We advised the client to register separate sitekeys for their production and staging sites. This can be done by unregistering WPML on the staging site through Plugins -> Add New -> Commercial and then registering it with a new sitekey. Additionally, we recommended coding the sitekeys into the
wp-config.php
file for easier management between environments. Detailed steps for this process can be found here: Automatic WPML Registration Using PHP. For sharing translation credits between staging and production, we provided guidance on setting up an automatic translation subscription for multiple sites, which can be accessed here: Automatic Translation Subscription for Multiple Sites.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
