Problem: The client experienced issues with their QA site (qa.instron.com) displaying the same credit balance as the production site after cloning and attempting to manage sitekeys and credits through WPML. Despite unregistering and re-registering the sitekey for the QA site, the credit balance remained unchanged, and the QA site disappeared from the WPML account's manage credits page. Solution: We recommended a complete refresh of the registration process to ensure proper synchronization between the QA site and the WPML account. The steps included: 1. Removing any existing QA site registrations from the WPML account. 2. Unregistering WPML from the QA site via the WordPress dashboard. 3. Generating a new site key for the QA site and registering it without assigning specific credits. 4. Verifying the credit display and site listing on the WPML account. Despite these steps, the issue persisted, indicating a deeper synchronization problem possibly related to how WPML handled the site as a 'copy' during the registration process. We then explored details of the migration wizard settings used during the process.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Please also check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can contact us directly at the WPML support forum.
Problem: If you're experiencing issues with auto translation not working for Saved Rows in Beaver Builder when using WPML, it might be due to a compatibility issue. The content of Saved Rows does not appear in the Advanced Translation Editor, preventing automatic translation. Solution: We recommend the following steps to address this issue: 1. Enable Beaver Builder Template Translation: - Go to WPML → Settings. - Open Post Types Translation. - Find “Templates (fl-builder-template)”. - Change it from Not Translatable → Translatable – only show translated items. - Click Save. 2. Send Templates and Pages for Translation: - Go to WPML → Translation Dashboard. - You will now see a new section for Beaver Builder Templates. - Select the Beaver Builder template (the saved row) and the page that uses this saved row. - Scroll down and send for translation. 3. Complete the Translation: - If you use Automatic Translation, WPML will translate it. - If translating manually: - Go to WPML → Translations. - Open the job and finish the translation. 4. IMPORTANT Manual Step (Required Every Time You Use a Saved Row): A. Open the Translated Page in Beaver Builder: - Go to Pages and open the page that contains the saved row. - Click the three dots (top right) and disable Fullscreen Mode so you can see the top admin bar. - Use the language switcher to switch to the translated language (e.g., Spanish). - Click Edit Anyway. - Launch Beaver Builder in the translated version of the page. B. Re-select the Translated Saved Row: - Click the module/element where you insert the saved row. - Click Edit. - The saved row is not selected by default. - Manually select the translated version of the row. - Save and publish the translated page.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
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: You are using WPML with Beaver Builder and have set up separate domains for different languages. However, when you switch languages in the WP Admin panel, the 'wp-wpml_current_language' cookie does not update correctly. It shows 'en' instead of 'ja', and when switching from the English domain to the Japanese domain, two cookies with values 'en' and 'ja' appear. Solution: We have identified that this issue might be related to custom code that alters WPML's default behavior. We recommend checking any custom code that might interfere with WPML's handling of cookies. Additionally, we suggest using WPML Hooks as a possible workaround for managing cookies across different domains. You can find more information on WPML Hooks here: WPML Hooks Reference. If this solution does not resolve your 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: The client reported receiving a notification from WPML indicating a change in the site's domain address, even though no changes were made. The message suggested that the site had moved from 'https://www.xyz.com' to 'https://xyz.co.kr', a domain the client does not recognize or use. Solution: 1. We suggested that the false message might be due to WPML detecting the site on a different domain. For more details, see the documentation on using WPML on two domains. 2. To address this issue: - Navigate to WPML → Support and click on the Troubleshooting link. - On the WPML Troubleshooting page, click the button labeled 'Force-enable WPML’s Advanced Translation Editor'. 3. If the issue relates to using an existing WPML site key for a different URL, which is not supported, the client may need to re-register the keys. Instructions for this can be found at removing development site notice after moving to production.
If these steps do not resolve the issue or if the solution 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 the problem persists, 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.
