Problem: The client's subscription was automatically renewed, and they no longer require the WPML plugin. They were not notified about the renewal and now wish to request a refund. Solution: If you're experiencing a similar issue with an unwanted subscription renewal, we recommend contacting our sales team directly to handle your refund request. Please email them at hello@wpml.org.
Remember, if you encounter any technical issues or need assistance with WPML in the future, we are always here to help.
Please note that this solution might be outdated or not applicable 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 this does not resolve your issue, please do not hesitate to open a new support ticket with us.
Problem: You are experiencing issues with your website translations and encountering errors. Solution: 1. Navigate to your Dashboard > Pages. 2. Open the edit screen of the original page and make a minor change, such as adding an extra blank space at the end of a sentence or paragraph. 3. Save the changes. A circular arrow should appear beside the second language links, indicating that an update is required. 4. Edit the translation again and ensure it is saved up to 100% translated. 5. If the issue persists, check the WordPress Dashboard > WPML > Translation Dashboard for a dialog box asking you to migrate the website. If present, complete the setup following the instructions at this link. 6. If no dialog box is present, unregister and re-register WPML: - Navigate to WordPress Dashboard > Plugins > Add New > Commercial (Tab). - Click the "Unregister WPML" link. - Click the "Register WPML" on the right section of the screen. - Follow the process to get a new site key and enter it. For more details on registration, visit this link. 7. If the problem still exists, navigate to WordPress Dashboard > WPML > Support > Advanced Translation Editor (Error Log) and report the error seen at the top row of the table.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client, António, reported that after translating and synchronizing the navigation menu on their website from English to French, German, and Portuguese, only the original English menu was appearing. Despite following provided tutorials and videos, the issue persisted. Solution: We advised António to first ensure that all content linked by the menu items was translated. This involved checking the translation status via WPML -> Translation Dashboard and translating any content that was not yet available in the desired languages. Additionally, we suggested checking for custom links in the menu under Appearance -> Menus and ensuring these were correctly configured in WPML -> String Translation. If the 'Look for strings while pages are rendered' option was missing, we recommended switching to human support for more personalized assistance.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Also, please 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 our support team directly at the WPML support forum.
Problem: If you click on English, a popup template with an Elementor Pro loop grid widget appears. In the second and third columns on desktop, the custom CSS for the loop items is missing, although the items are translated. The popup items look correct in English but appear strange in other languages, with the editor showing white but visible in the Structure Panel. Solution: We have developed a small plugin to address this issue temporarily. Please back up your website first. Then, download and install the plugin from this link. After installation, make a minor change to the original page and ensure it is 100% translated. This should resolve the problem temporarily. Our development team is aware of the issue and is working on a more permanent solution.
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 reported a critical issue with WPML Advanced Translation Editor (ATE) on a live WooCommerce + WPML multilingual store. When sending a product for automatic translation using ATE, the translation process crashed and created fatal errors, specifically an 'InvalidArgumentException'. Despite several actions such as clearing WPML cache, switching to Classic Translation Editor, and deactivating conflicting plugins, the issue persisted. Solution: We performed several troubleshooting actions under WPML → Support → Troubleshooting. After these adjustments, we tested translations on the client's site with successful results in both Arabic and Persian using ATE. We asked the client to verify if the issue was resolved on their end and to check if the translations were performed correctly.
If you're experiencing similar issues, we recommend trying the following steps: 1. Navigate to WPML → Support → Troubleshooting and run the necessary troubleshooting actions. 2. Ensure that your Automatic Translation account ID is correctly updated and matches the records. 3. Test the translation with a few products to confirm functionality.
Please note that this solution might be irrelevant if it's 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 at WPML support forum for further assistance.
Problem: How to translate a string that is in a PHP snippet. Solution: If you're experiencing this issue, we recommend wrapping the text in a WordPress gettext function so that WPML can detect it when scanning the code. Here's a step-by-step guide:
After updating the snippet, navigate to WPML → Theme and plugins localization, scan the relevant source if available, then go to WPML → String Translation and search for the text to add its translation. For more details, visit our developer documentation: https://wpml.org/documentation/support/how-to-use-gettext/
Please note that this solution might be irrelevant if it's 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: The client set up a title bar image for each page using Avada layout section and defined the title and image location in Avada page options. After translating the first page, the title bar image did not appear on the translated page. Solution: 1. Navigate to WPML -> Settings and scroll to the Custom Field Translation section. 2. Search for fields starting with pyre_ or fusion_ (Avada's prefixes for Page Options). 3. For title bar background images and retina images, set them to Copy if the same image is desired across languages, or Translate if different images are needed per language. 4. Set heading and subheading text fields to Translate. 5. Click Save at the bottom of the page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 at WPML support forum for further assistance.
