Problem: The client frequently updates their QA server with data from the production environment, which involves changing URLs and reactivating WPML. This process often results in site keys becoming inactive and a loss of translation credits. The client seeks a way to synchronize the QA and production environments without losing credits and to recover lost credits. Solution: 1. Ensure that the QA domain name remains consistent when reactivating WPML to avoid unnecessary site key changes. 2. Navigate to WPML > Support > Troubleshooting Link and share the Advanced Translation Editor ID for both production and staging sites. 3. We have resolved issues on our translation server that were causing lost credits and multiple activations with the same domain name. This should prevent similar issues in the future. 4. Always generate a new sitekey when activating WPML on a new domain to avoid conflicts.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is trying to resynchronize their production database and files onto their QA server. They encountered an issue where both the QA and Production servers showed 2 connected sites instead of 1, complicating their attempt to share prepaid credits between these environments. The production account displayed as having no credits, while the QA showed one credit. Solution: We recommended that the client should deregister and then re-register the sitekey for their QA domain. This can be done by copying the sitekey, navigating to WP > Plugins > Add new > Commercial Tab, and performing the deregistration and registration process. This should resolve the issue of the site showing as 'Inactive' and help in correctly displaying the connected sites and sharing credits.
If this solution does not resolve your issue, or if it seems outdated or not applicable to your 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.
Problem: The client's staging site was showing as unregistered and unable to save the site key, while the QA environment on the same VM was functioning correctly. The client was concerned about a potential block from WPML's side affecting their staging environment. Solution: We first asked the client to check if there were any red X icons in the WPML > Support > Installer support section, which would indicate a connection issue to the WPML API. Upon confirmation of a red X, we recommended whitelisting the following domains with their hosting provider's help:
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are working on a development site and encountering an issue where certain links do not fall back to the default language on the German version of the page, resulting in a 404 error. Some links like 'ASTM C365' correctly fall back, but others like 'ASTM C109' and 'ASTM C170' do not. Solution: We recommend you apply the following workaround to address the fallback issue: 1. Edit the file at
3. After line 458, add a new function to handle the page path and post type processing more effectively. This function also includes improved caching mechanisms and SQL queries to ensure correct page retrieval based on the language settings.
After implementing these changes, please verify if the language switcher functions as expected.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, 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.
