Problem: When duplicating an event into French using The Events Calendar with WPML, the event start/end times, venue, and organizer details are not duplicated correctly. The start and end times appear blank, the date resets to the current day, and the organizer and venue revert to default settings. Solution: If you're experiencing this issue, we recommend trying the following steps: 1. Instead of duplicating the event, try creating a translation of the event to see if this resolves the issue. 2. Clear all server caches on your site. 3. Edit your
wp-config.php
file and add the line
define('WPE_GOVERNOR', false);
once.
If these steps do not resolve your issue, or if the solution becomes outdated, 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: The client wants to change their WPML subscription from Multilingual Agency to Multilingual CMS. Solution: We recommend waiting until your current subscription expires. After it expires, you can log in to your account and purchase the new Multilingual CMS subscription. To prevent your current subscription from renewing automatically, please disable automatic renewal by following this guide: https://wpml.org/faq/cancel-wpml-subscription/
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 open a new support ticket.
Problem: The client experienced performance issues with their webshop when using WPML and WCML's currency switcher. They are considering using a lightweight currency switcher, specifically Curcy Pro (paid version), and need to know if it is compatible with WPML without causing performance degradation. Solution: We recommend contacting Curcy's support service to confirm if their plugin is compatible with WPML. Additionally, you can refer to a related issue discussed in our forums: https://wpml.org/forums/topic/after-changing-to-other-currency-cant-change-back-to-default-currency-usd/ which was resolved by LiteSpeed developers.
Please note that the solution provided 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 the issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're using BeTheme with WPML and notice that English posts display the excerpt correctly above the featured image, but German posts translated via WPML do not show the excerpt (the wrapper gets class no_content and is empty), even though the excerpt is saved correctly in the database. Solution: We recommend following these steps to resolve the issue: 1. Ensure that the BeTheme template is fully translated and synchronized. This was the root cause in a similar case. 2. Check the BeBuilder data storage settings and ensure they are set to 'Serialized', and that 'mfn-page-items' is set to 'Translate' in WPML Custom Fields. 3. Visit the documentation on making BeTheme content available for translation. If these steps do not resolve the issue, it 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 the problem persists, please open a new support ticket.
Problem: After migrating a site from a staging environment to production, the Advanced Translation Editor (ATE) cloud was rejecting all translation jobs with an HTTP 426 error, indicating a URL change. The client attempted various troubleshooting steps, including reactivating WPML plugins and confirming site key registration, but the issue persisted. Solution: We recommended the client to re-save the original pages in the default language (DE) to refresh the database entries. This action allowed the ATE to recognize the correct production URL and accept translation jobs. The client confirmed that after re-saving the affected pages and updating the translations, the issue was resolved.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client reported that although the plugin strings are fully translated into Hebrew, some strings are not displayed in the backend of the Amelia plugin. Even though these strings appear translated in the string translator, they need to be manually saved again to be visible. Solution: We recommended the client to provide examples of strings that are translated but not showing. This would allow us to investigate further and identify whether the issue is with the string translation saving process or another aspect of the plugin's integration with WPML. If the strings are not appearing in the string translator, it might indicate that the plugin's files need to be updated by the plugin author to ensure compatibility with WPML.
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 the issue persists, please open a new support ticket at WPML support forum.
Problem: You receive a notification that a file within the folder wp-content/plugins/wpml-string-translation/lib/StringScanning/vendor/wp-cli/php-cli-tools/lib/cli/unicode/regex.php is identified as malware by the Malcure Malware Shield plugin. Solution: We have confirmed that this alert is a false positive. It will be addressed in a future WPML release, and the alert should no longer appear once the fix is included.
If this solution becomes irrelevant due to updates or if it does not resolve your issue, we 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.
Problem: If you're experiencing an issue where you receive an error stating 'Failed to get parameters to initialize ATE dashboard: Empty or invalid response' when trying to register a new site and initialize the ATE dashboard, this summary is for you. Solution: We recommend the following steps to resolve this issue: 1. Ensure that your server is responding correctly and that there are no network issues that might be blocking the dashboard initialization. 2. Check your site’s console for any JavaScript errors that could be interfering with the ATE dashboard. You can do this by right-clicking on your web page, selecting 'Inspect', and navigating to the 'Console' tab to look for errors. 3. Clear your browser cache and cookies, as these can sometimes cause issues with loading new settings or updates. 4. If the problem persists, it might be due to a compatibility issue with another plugin or theme. Try deactivating other plugins temporarily to see if the issue resolves. 5. Update all your themes and plugins to the latest versions to ensure compatibility and security.
If these steps do not resolve the issue, or if the solution seems irrelevant because 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 you still need assistance, please open a new support ticket with us at WPML support forum.
Problem: If you're trying to translate product option names and they remain in the original language on the translated product page within the admin interface, despite enabling 'Auto-register untranslated strings' and disabling caching, this might be due to a compatibility issue between the plugin and WPML. Solution: We recommend replicating the issue on a clean installation to help identify and report the compatibility issues more effectively. Here are the steps we suggest: 1. Install the plugin on a clean WordPress and WPML setup. 2. Add an option with the plugin to one of the products and attempt to translate it. 3. Try to replicate the issue. It's important to note that the WPML Advanced Translation Editor is not supported by some plugins, and the Native WordPress Editor should be used instead. More details can be found here: Plugin Documentation. If the developers of the plugin do not make that section compatible with the translation editor, we will explicitly mention that in our compatibility report page, which you can check here: WPML Compatibility Report Page.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
Problem: The client reported slow load times when the WPML String Translations plugin is enabled. They noticed that disabling the plugin significantly speeds up the page loads. They also mentioned using the Index WP MySQL For Speed plugin, which only slightly improved the situation. The client was concerned about the storage of translation files and the potential impact of custom actions on performance. Solution: We recommended the following steps to troubleshoot and potentially resolve the issue: 1. Use the Query Monitor plugin to compare performance with and without WPML plugins enabled to help identify slow queries. 2. Ensure all WPML plugins are updated to the latest versions. 3. Test in a minimal setup by switching to a default theme, such as Twenty Twenty-Four, and disabling all plugins except WPML and ACF. Then, gradually re-enable the theme and other plugins to check if a specific component is causing the issue. 4. If the issue persists with only WPML and the default setup, it might be a WPML-specific issue, which we will investigate further. 5. Check with the hosting provider to review server load, cache, or configuration differences, as the local environment was much faster than production. 6. If applicable, provide a staging site or a duplicator package for further investigation. 7. Since the issue related to a read-only languages directory mentioned in the Pantheon errata does not apply (as translations are being generated and stored), there is no need to apply the workaround in wp-config.php. 8. Removing the
after_setup_theme
action could help improve performance if it was doing additional processing on every request.
If these steps do not resolve the issue or if the solution 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that videos and images were not displaying correctly on the Danish version of their product pages compared to the English version on their WooCommerce site using the JetixWP plugin. Solution: We recommended the client to first update WPML and its addons to the latest versions by following these steps: 1. Create a backup of the website. 2. Navigate to WordPress Dashboard > Plugins > Add new > Commercial (tab). 3. Click the Check for Updates button and update WPML and its addons. For more information on automated updates, visit https://wpml.org/faq/install-wpml/#automated-updates. Next, ensure media translation settings are correctly configured: 1. Go to WordPress Dashboard > WPML > Settings > Media Translation. 2. Check all enabled checkboxes and click the Start button. 3. Wait for the process to finish. Then, make a minor edit to trigger an update: 1. Navigate to Dashboard > Products and open the edit screen of the original product. 2. Make a small change and save it. 3. Edit the translation again and ensure it is 100% translated. Additionally, we enabled the COPY option for specific custom fields related to video features, which resolved the issue.
If this solution does not apply to your case, or if it seems outdated, 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.
Problem: The client has set up their site with WPML currency triggered by geo location using a MaxMind account. However, they are experiencing issues where shoppers see several items in their cart, but some items disappear during checkout. They suspect this is due to the currency setting by geo location. Additionally, the client is concerned about the WPML migration banner on their staging site, which was cloned from the production site, as they fear it might affect their live site. Solution: We recommend testing the issue on the staging site with only the essential plugins active: WPML, WooCommerce Multilingual (WCML), WooCommerce, and any other strictly required plugins. This approach will help determine if a third-party plugin is causing the issue. Regarding the WPML migration banner, you can safely mark the staging site as a copy, which will not affect your live site. If you do not plan to use translations on the staging site, you can skip the migration. However, if you need to test translations properly, such as updating original content and syncing translations, you should complete the migration process.
If this solution does not resolve your issue or seems outdated, 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.
Problem: The client needed assistance with an issue related to WPML currency settings. Solution: We recommended continuing the discussion on the existing support ticket specifically opened for this issue. For further details, please visit the support thread at https://wpml.org/forums/topic/wmpl-currency/.
If this solution does not apply to your case, or if it seems outdated, we encourage you to open 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 https://wpml.org/forums/.
Problem: The client has set up their site with WPML currency triggered by geo location using a MaxMind account. However, they are experiencing an issue where shoppers see several items in their cart, but when they proceed to checkout, several items disappear. The client suspects this is due to the currency setting by geo location. Additionally, after cloning the production site to a staging site for troubleshooting, WPML detected a change in the site's URL, prompting a migration request, which the client is hesitant to proceed with due to concerns about affecting the live site. Solution: We recommend checking the configuration settings for the WPML currency and geo location to ensure they are correctly set up. It's possible that the settings might be causing conflicts during the checkout process. For the issue related to WPML's migration request after detecting a URL change on the staging site, it is generally safe to proceed with the migration as it should not affect the live site. However, if you are unsure or need further assistance, we advise you to continue the discussion in your existing support ticket here: https://wpml.org/forums/topic/wmpl-currency/
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 the problem persists, please open a new support ticket for personalized assistance.
Problem: If you're experiencing issues with the Advanced Translation Editor (ATE) where translation jobs intermittently fail, particularly when sending products for translation to Arabic, and the request payload incorrectly contains:
"language_code": "callable"
instead of:
"language_code": "ar"
This error leads to translation jobs being created successfully but then failing or behaving inconsistently afterward. Solution: We recommend checking if this issue is similar to one previously reported. You can follow the ongoing support in your original ticket here: https://wpml.org/forums/topic/i-am-getting-issue-with-automatic-trasnlations/
If this solution seems outdated or not applicable to your case, please open a new support ticket. 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.
For further assistance, please contact us through the WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
