Problem: You are attempting to add four new languages (Dari, Pashto/Pashto, Tigrinya, Farsi) to your site using the WPML plugin, but encounter an error that deletes input data for these languages. Solution: We recommend deactivating every language in your WPML setup and then trying to add the new languages again. If the issue still occurs, share a screenshot of what you are entering. This will help us better understand and address the issue.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at 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 was experiencing an issue where WPML reported 'WPML doesn't manage the translation' when attempting to update translations for previously translated Chinese articles. The problem persisted even after trying features on the WPML troubleshooting page and changing the PHP version. Solution: We advised the client to downgrade the PHP version from 8.5.5 to 8.2 or 8.3 and check if the issue was resolved. After downgrading, the issue seemed to disappear, which might have been aided by the flushing of an outdated cache memory file. If you're experiencing similar issues, we recommend trying the following steps: 1. Downgrade your PHP version to 8.2 or 8.3. 2. Clear your site's cache. 3. Confirm that the issue is resolved.
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 at WPML support forum.
Problem: On translated product category archive pages, Yoast outputs the wrong language SEO title and meta description. Although the backend shows correct localized Yoast SEO fields for each category, the frontend displays incorrect language data. Solution: 1. If you're experiencing this issue, it's important to note that from WPML SEO 2.2.0 onwards, term meta such as SEO titles and meta descriptions for categories can be translated via WPML → Translation Dashboard as String Packages. This integration allows for automatic translation along with the rest of the site. 2. However, if you have manually added translations in the category editing screen, these may not appear on the frontend with versions starting from WPML SEO 2.2.5. WPML now requires these fields to be translated via the Translation Dashboard. Available options: - Roll back to WPML SEO 2.2.4 to continue using manual translations. - Use the WPML Translation Dashboard (String Packages) for translations, which is the recommended method moving forward.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 experiencing an issue where after translating a template in Bricks Builder using WPML, only the English version of the template appears in the template picker, and other language versions are missing, this might be due to the admin language settings. Additionally, all previously assigned templates might display a raw post ID instead of the template name. Solution: We recommend checking the language settings in your user profile on your WordPress site. Specifically, you should ensure that the option 'Set admin language as editing language' is not selected if you are working in a multilingual environment. This setting can cause Bricks Builder to load templates only in the currently set admin language, hence not showing other language versions in the template picker. After adjusting this setting, reopen Bricks Builder and check if the template picker now correctly displays templates in all languages.
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 the problem persists, please open a new support ticket.
Problem: If you're experiencing issues with the Dual Color Heading widget from UAE for Elementor not translating correctly, where only two of the three strings appear in the Advanced Translation Editor, and the translations do not display in French, you might be facing a configuration issue. Solution: The issue has been reported to the plugin author. In the meantime, we recommend updating your WPML configuration. Here is the suggested configuration to ensure that the Dual Color Heading widget translates properly. Add this config to WPML > Settings > Custom XML Configuration:
<wpml-config>
<elementor-widgets>
<widget name="eael-dual-color-header">
<conditions>
<condition key="widgetType">eael-dual-color-header</condition>
</conditions>
<fields>
<field type="Dual Color Heading: Title ( First Part )" editor_type="LINE">eael_dch_first_title</field>
<field type="Dual Color Heading: Title ( Last Part )" editor_type="LINE">eael_dch_last_title</field>
<field type="Dual Color Heading: Sub Text" editor_type="VISUAL">eael_dch_subtext</field>
<field type="Wrapper Link" key_of="eael_wrapper_link" editor_type="LINK">url</field>
</fields>
<fields-in-item items_of="eael_dch_multiple_titles">
<field>eael_dch_title</field>
</fields-in-item>
</widget>
</elementor-widgets>
</wpml-config>
This configuration should help in correctly recognizing and translating the widget. You will now need to edit the widget on the original content, save the page or post you are working on, and then update the translation. 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client purchased a 1yr subscription to "WPML Multilingual CMS" and is considering upgrading to "WPML Multilingual Agency" due to hosting 26 client sites on a WordPress multisite network, each with multiple environments, totaling 78 sites. Solution: We informed the client that when using Multisite, it is only necessary to register the main site using the site key. There is no need to register the subsites, as this is not supported.
If this solution does not fully address your concerns, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported a significant visual discrepancy between the original English blog page and its Hungarian translation in Bricks Builder. Specifically, the header is not appearing as expected. Solution: If the menu items are too long, causing layout discrepancies, we suggested manually translating the menu to adjust the length of the items. For more detailed guidance, we provided a link to our documentation on translating menus: https://wpml.org/documentation/getting-started-guide/translating-menus/
If the solution provided does not resolve the issue or seems outdated, or if it does not apply 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, you can also visit our support forum at https://wpml.org/forums/.
Problem: A product with French as the default language was being incorrectly translated into Spanish instead of English, despite Spanish not being an active language on the site. Solution: 1. We recommended checking the active languages in WPML settings to ensure Spanish was not enabled. 2. We suggested checking for stray Spanish translations in the trash and deleting them if found. 3. We advised updating WPML plugins and verifying the correct language mapping for English. 4. We instructed the client to edit the product in the original language, make a minor change, save it, and update the translation. 5. The issue was resolved after resending the product for automatic translation.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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.
Problem: If you're experiencing issues with activating WPML on a subsite in a WordPress multisite installation with subdirectory configuration on top of Nginx, and encountering an error stating that the WordPress REST API must be enabled, this might be due to Nginx rewrite rules not properly handling the language-prefixed REST URL. Solution: We recommend adjusting your Nginx rewrite rules to correctly rewrite URLs for WPML's REST API checks. Here's an example of how you can modify your rewrite rules:
rewrite /wp-admin$ $scheme://$host$uri/ permanent;
# one or two prefixes before wp-* (e.g. /masse/wp-json or /masse/en/wp-json)
rewrite ^(/[^/]+)?(/[^/]+)?(/wp-.*)$ $3 last;
rewrite ^(/[^/]+)?(/[^/]+)?(/.*\.php)$ $3 last;
After updating the rules, remember to reload the server, clear all caches, and resave permalinks in WordPress. 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 at WPML support forum.
Problem: You are having trouble with media translation not displaying the correct logo when switching languages in your WordPress site. Solution: We recommend following these steps to resolve the issue: 1. Locate the image ID in the WordPress media library for the logo. 2. Use WPML string translation to assign the correct image ID for each language version. 3. Upload and select appropriate images for each language and update the translation accordingly.
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: If you've just purchased credits and assigned them to your site, but upon refreshing, the credits still display as zero. Solution: We recommend following these steps to resolve the issue: 1. Visit https://wpml.org/account/sites/ and delete the existing site key, then generate a new one. 2. In your WordPress dashboard, go to Plugins → Add New. 3. Open the Commercial tab. 4. Click Unregister WPML. 5. Register WPML again using the new site key.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are unable to apply translations. Solution: We recommend that you first edit the original content and save it. After saving, attempt to apply the translation again. If this does not resolve the issue, it may be due to reasons that have become outdated or might not apply 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 at WPML support forum for further assistance.
Problem: The client wants to edit the link of the menu logo in every language on a website using the DIVI theme builder. Solution: We tested changing the logo URL to the homepage URL, and it worked correctly. If you're experiencing this issue, we recommend checking if setting the logo URL to the homepage resolves the problem. If you prefer to use a custom URL for the logo in different languages, please confirm this preference.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where Yoast SEO titles and meta descriptions for taxonomy archive pages (product categories and product attribute archives) are always displayed in English on the frontend, despite being correctly translated in the backend. This problem occurred after a server migration and updates.
Solution: We recommend the following steps to address the issue: 1. Ensure that the original SEO strings for taxonomies are translated via the WPML → Translation Dashboard, where a string package containing all related terms is available. 2. Avoid adding translations directly via String Translation as it can overwrite values from the string package, leading to inconsistencies. 3. After translating, use the Yoast Test Helper plugin to reset the Yoast indexables tables, ensuring that changes are reflected on the frontend. This can be done by navigating to Yoast Test Helper plugin → Reset indexables tables. 4. If issues persist, consider rolling back to a previous version of the SEO plugin as suggested by our developers, and follow the guidance provided in the errata: https://wpml.org/errata/wordpress-seo-issues-translating-yoast-seo-term-meta/
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 at WPML support forum for further assistance.
Problem: The client was experiencing ERR_TOO_MANY_REDIRECTS errors and issues with translations not appearing correctly on the Events page after changing languages. Solution: Firstly, we resolved the redirection issue by updating the URL slug translations. We navigated to WPML → Settings → Post Type Translations and set the event slug to "event". We also recommended translating the slug from the same location. For more details on translating page slugs, visit Translating Page Slugs Documentation.
For the translation issue on the Events page, we suggested making a small change on the original Events page and then completing the translations.
Additionally, our compatibility team provided a code snippet to address further issues with WPML on the Events page. The client should add the following code at the end of the file located at
If these solutions do not resolve the issue or seem 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive