Problem: You are unable to find the option to use DeepL as a translation service for the Spanish (Mexico) language variant. Solution: We recommend verifying the list of supported languages by DeepL and other translation engines here. For Mexican Spanish, you should use WPML’s Professional Translation Cloud (PTC), which is the default engine for WPML Automatic Translation and supports dialect-specific language variants, including Spanish (Mexico). Ensure that Automatic Translation is enabled and that WPML is set to use the PTC engine. If you need to translate content, you can either use the Advanced Translation Editor by clicking the plus icon or send the page for automatic translation via WPML → Translation Dashboard. Select the page, choose the target language, and send it for automatic translation.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.
Problem: You want to confirm if the Spanish language option in WPML covers the Mexican dialect. Solution: Currently, major translation engines like DeepL, Google, and Microsoft do not support Spanish dialect variants. However, Mexican Spanish is specifically supported when using WPML’s Professional Translation Cloud (PTC) engine. This engine is the default in WPML’s Automatic Translation and it supports dialect-specific variants. The cost for using this service is 4 credits per word. You can view the full list of supported languages and dialects here.
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.
Problem: You are using global modules with WPML in Divi and have set translations for these modules in the Divi Library. However, when placing the global module on a page, WPML still prompts for translations on the page itself and ignores the translations set in the Divi Library. Solution: First, ensure you have followed the steps outlined in the documentation for translating Divi and Extra global modules with WPML. You can find the guides here:
If the problem persists after following these guides, consider switching from the Classic Translation Editor to the Advanced Translation Editor for more flexibility with translations.
If these solutions do not resolve your issue or seem outdated, we recommend opening a new support ticket. We also advise 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: You are using the Better Search Replace plugin, which is compatible with WPML, to replace words across different language pages on your site. However, after using the plugin, the changes are visible on the English and Belgian pages, but the Classic Editor still shows the old content. Solution: The issue arises because the plugin modifies the database directly, which does not trigger the necessary WordPress hooks to update the Advanced Translation Editor (ATE). Unfortunately, WPML does not have a built-in tool to address this directly. However, we recommend updating your posts programmatically as a workaround. This method has not been fully tested by us and is not officially supported by WPML, so please ensure you have a full website backup before proceeding. For guidance on how to update posts programmatically, you can refer to this document: https://wordpress.stackexchange.com/questions/330746/how-can-i-mass-update-save-all-wordpress-posts-and-pages.
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 at our support forum.
Problem: You are experiencing an issue where the language switcher is appearing on pages that do not have translations. Solution: If you want to prevent the language switcher from showing on pages without translations, we recommend you follow these steps: 1. Navigate to the WPML >> Settings page. 2. Scroll down to the "Post Types Translation" section. 3. Set the Pages post type to "Translatable - only show translated items". 4. Clear all types of cache on your site/server/CDN to see if this resolves the issue.
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 for further assistance.
Problem: If you're using the 'Don't update translation' button in WPML and expecting changes in the original language to automatically update in other languages, but find that this isn't happening, you might be misunderstanding the function of this button. The 'Don't update translation' button is designed not to update translations when changes are made to the original language. Solution: We recommend checking the functionality of the 'Don't update translation' button by following these steps: 1. Make changes to your page in the original language. 2. Click the 'Don't update translation' button in the language sidebar. 3. Verify if the translations remain unchanged, as this is the expected behavior. If you need to see the changes reflected in other languages, you should not use the 'Don't update translation' button. For further assistance, please provide screenshots of your process, including the use of the 'Minor Edit' button and the resulting status of translations. Additionally, enable and provide debug information by following the instructions here: http://wpml.org/faq/provide-debug-information-faster-support/
If this solution does not apply to your situation, 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: If you're experiencing issues with language flags not displaying when using a shortcode in WPML, it might be due to the page not having translations available. Additionally, the flags might not be set up correctly under the custom flag settings. Solution: First, ensure that the language flags are correctly configured in WPML. You can do this by navigating to WPML > Languages > Site Languages > Edit Languages > Custom flag. Here, you can adjust or replace the flag, such as changing it to the USA flag.
If the issue is related to the flags not appearing because the page lacks translations, you can enable the display of secondary languages even if they don't have translations. Go to WPML > Languages > Language switcher options > How to handle languages without translation and select 'Link to home of language for missing translations'.
Additionally, if you notice any style issues with the display of the language flags, you might need to apply custom CSS. Here is an example of CSS that could help:
For more details on fixing styling and CSS issues, you can visit this documentation.
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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing errors with WPML after upgrading your hosting server to PHP 8.2, such as deprecated notices for dynamic properties in WPML_LS_Menu_Item, you are not alone. Solution: We recommend updating WPML to the latest version, specifically WPML 4.6.13, which addresses these issues. You can update the plugins to their latest versions by following the steps provided in our documentation here: WPML Documentation.
If this solution does not apply to your case because it might be outdated or not relevant to your specific situation, 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 our support forum.
