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.
Problem: If you're trying to fix technical SEO issues like improper URLs and need these changes to propagate to different language versions of your site, you might encounter issues where changes do not always apply. This could be due to issues in the Media Translation add-on, specifically causing double slashes (//) in media links. Solution: First, ensure you have a backup of your site. Then, if you're comfortable with code changes, you can manually edit the file at
Save the changes. However, this is a temporary workaround. We have released WPML 4.9.3, which includes a permanent fix for this issue. You can download the new version from https://wpml.org/account/downloads/. After updating, you can remove the manual code edit.
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 at WPML support forum.
Problem: The client is experiencing difficulties with duplicated pages and wants to eliminate all languages except the main language (de-at) from their WPML setup. They have also inquired about a cleanup plugin for removing languages. Solution: We recommend the following steps to effectively delete a language and clean up your site: 1. Delete or trash translated posts/pages/products for the language you no longer need. 2. Remove menus, widgets, and templates assigned to that language. 3. Remove String Translation entries that are specific to that language. 4. Clear all caches (plugin, server, CDN) after these changes. 5. Resave permalinks from Settings > Permalinks. For SEO considerations, since you are removing the language, consult with your SEO agency about redirecting links to avoid losing traffic.
If this solution does not fully address 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue with the WPML Translation Dashboard where the 'Words to translate' spinner never resolves, and the browser DevTools shows a 500 Internal Server Error for the endpoint '/wp-json/wpml/v1/get-words-to-translate-for-items'. Other related WPML REST endpoints function correctly. This problem persists despite extensive troubleshooting, including disabling plugins, switching themes, and disabling security measures. Solution: We have addressed a similar issue in a recent support forum post. We recommend checking the solution provided there to resolve the REST API 500 error. Please visit the following link for detailed instructions: WPML support forum post.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Additionally, 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 also contact us directly through the WPML support forum.
Problem: You are experiencing an issue where all translated pages are incorrectly using the same special header as the home page instead of having different headers like in the English version. Solution: We recommend translating the page templates and header copy templates through WPML → Translation Dashboard. After translating, make a small change to the page templates and update the translations. This should resolve the issue with the headers on the translated pages.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and verify 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 for further assistance.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
