Problem: The client was experiencing an issue where some strings in a Gravity Form were not appearing in the translated version, despite being scanned and set up in WPML's translation management. Solution: We identified this as a compatibility issue with the Gravity Forms conversational forms. To address this, we replicated the issue on our servers and escalated it to our compatibility team. We provided the client with a sandbox environment to replicate the issue: Sandbox Environment Instructions were given to download and activate the necessary Gravity Forms plugins and create a basic conversational form to see if the issue persists. Additionally, we discovered a workaround for the button translation issue in conversational forms, which can be found here: Workaround for Gravity Forms Button Translation Issue We advised the client to back up their site before applying the workaround.
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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: You are trying to approve translations for your 'how it works' page from English to Turkish, but when you click review, it just keeps loading and never opens. Additionally, the translated page displays a 'page couldn't find' message. Solution: We recommend first disabling all plugins except WPML to see if the issue persists. If the problem continues, you should enable debugging to identify the underlying issue. To do this, open your wp-config.php file and locate
define('WP_DEBUG', false);
. Change it to:
define('WP_DEBUG', true);
Also, to log errors to a file on your server, add:
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 the problem persists, please open a new support ticket with us for further assistance.
Problem: The client is experiencing issues with missing content on the homepage and products in the backend when trying to translate. Solution: We recommend the following steps: 1. Perform a minimal environment test by using a default theme (if applicable) and disabling all non-WPML and non-essential plugins to see if the error persists. It's advisable to make a backup of the site before doing this or to test on a staging copy. 2. Increase the WordPress memory limit as it's currently below the minimum requirements for WPML. Add the following code to your wp-config.php file right before the /* That's all, stop editing! Happy publishing. */ line:
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You want to change the English page title of your website from 'Petra Blunk' to 'Petra Blunk Art'. Solution: We recommend using the WPML String Translation module to translate the site title and tagline. Currently, you have access to the Multilingual Blog account type, which does not include this feature. You will need to upgrade to either the Multilingual CMS or Multilingual Agency account. You only need to pay the price difference for the upgrade. For detailed instructions on how to use the String Translation module, please refer to the following documentation links:
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where some fields are missing on the English translated page of a GravityForm, despite being present in the final POST request, this might be due to the translation settings. Solution: We recommend not translating the choice and value fields in your forms, as this can cause them to be truncated in email notifications. This is particularly important when using conditional fields. If you've already translated these fields, try reverting the translations. Additionally, ensure that you are not using any third-party plugins or themes that could be affecting the form's functionality. You can test this by importing the form into a clean sandbox environment to see if the issue persists.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please 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, you can contact us directly through our support forum.
Problem: The client experienced an issue where switching to French on their WordPress site resulted in a blank page. This occurred after changing the URL structure to "lang=fr" and attempting to translate the menu. Solution: We identified that the problem was linked to the "Elementor Single Page #732" template. We resolved the issue by setting this template to Draft status instead of Published.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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 visit our support forum at WPML Support Forum.
Problem: You are experiencing a CORS issue where your .at domain is incorrectly sourcing its files from the .ch domain instead of the primary translation. This misconfiguration causes icons and fonts to be blocked due to CORS policies. Solution: We recommend reaching out to your web hosting provider and requesting them to set the CORS policy specifically with the
Access-Control-Allow-Origin
header. This adjustment will allow your .at domain to correctly load content from the intended source domain. For detailed guidance on setting CORS policies, please visit: https://enable-cors.org/
If this solution does not resolve your issue or seems outdated, please check for 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. Should the problem persist, we highly recommend opening a new support ticket for further assistance.
Problem: You redesigned your website and noticed that the secondary language version (English) of the ticket site has been directly edited in Elementor, differing from the primary language layout (Danish). The English version does not match the layout of the Danish version after direct edits were made in Elementor. Solution: If you're experiencing this issue, we recommend trying to make a small change to the original page and then translating it in the WPML translation editor. This should apply the original layout to the translation after saving it. If you directly added translations to Elementor for the secondary language, consider moving them to the WPML translation editor. Alternatively, you can edit the layout directly in Elementor for the secondary language. For guidance on translating an Elementor website with WPML, visit How to Translate an Elementor Website with WPML. Another option is to switch to the secondary language, move the page to the trash, and then permanently delete it from the Trash page for that language. For more details on this process, visit How to Delete the Translation of a Page.
If these solutions do not resolve your 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.
Problem:
Mega Menus aren't synchronised when updating the template
Solution:
Mega Menus were created individually from Appearance->Menus and they weren't connected so the update on the template were not shown on front-end.
Upon checking, we found out that it's impossible to defined existing template on the menus so suggested to contact the plugin author to ask if it's possible to define existing templates.
As a workaround, you can follow the below steps:
- Create a backup
- Delete the English translations of the template used, from trash too
- Connect two templates that mega menu is using as translations of each other.
Problem: On mobile devices, the language does not switch correctly even though the URL changes to the appropriate language suffix (e.g., /en). The content remains unchanged. Solution: 1. Ensure that all elements on the page, including text and templates, are fully translated. For instance, if you are using Elementor, switch to the mobile view in the Elementor editor to verify that all text is translated. 2. Specifically, check and translate the header template as it might not be translated, which could cause the content to not display correctly in the desired language. You can edit the header template here: Translating Theme Options
If this solution does not resolve your issue or seems outdated, we 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 visit our support forum at WPML Support Forum.
Problem: You are trying to add a new domain but cannot find the 'add new site' button. Solution: If you're experiencing this issue, it's likely because your account was initially set as a 'Site Owner' account, which is limited to one site only. We recommend creating a new WPML account. For more information, please check out the following link: https://wpml.org/purchase/transferring-account-renewals-to-your-clients/ If you are still within the 30-days refund period, you can request a refund here: https://wpml.org/purchase/refunds/ After processing your refund, please proceed to create a new separate WPML account.
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.
Problem: The client is trying to translate the footer contents and the contact form's submit button from Swedish to English using the WPML plugin on a WordPress site with the 'Alim' theme. Despite using the auto-translation feature and the translation management list, the footer remains untranslated, and specific strings for the footer and the submit button are not found in the translation editor.
Solution: 1. To address the untranslated contact form's submit button, edit the form by changing the strings from English to Swedish and then update the translation. Detailed steps for translating forms in Contact Form 7 with WPML can be found here: https://wpml.org/documentation/related-projects/using-contact-form-7-with-wpml/
If these solutions do not resolve your issue or seem outdated, we recommend opening a new support ticket. Also, 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, please visit our support forum: https://wpml.org/forums/forum/english-support/
Problem: You have a WooCommerce shop in English and Italian. A product tag '1970s' in English and its Italian translation 'Anni 70' are incorrectly displayed. The Italian tag shows under English tags with a wrong slug and fewer products than expected. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WPML > Support > Troubleshooting. 2. Click on the following buttons: - Clear the cache in WPML - Set language information - Fix terms count - Fix post type assignment for translations 3. Clear the caches from your site and browser. 4. Verify if the translated category still appears under the default language. If the problem continues, open the translated category, set the language information, and manually link the category with the default category. For guidance, watch this video.
If this solution does not resolve your issue or seems outdated, please 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, feel free to contact our support team at WPML support forum.
Problem: The client is setting up options pages to be translated using WPML and is experiencing issues where switching languages via the language switcher in the admin bar does not update the options page as expected. For example, changing the language to Chinese, saving the options page, and then switching back to English shows the same content as saved in Chinese. The fields in ACF are set to be translated, but they do not change language. Solution: We recommend the following steps to address the issue: 1. Go to WPML > Settings and scroll to the Custom Field Translation section. 2. Click on the Show system fields link. 3. Once the page is refreshed, enter the field name in the search box within the Custom Field Translation section. For example:
archive_heading_text
. 4. In the results, the field should appear twice, with one name starting with an underscore (e.g.,
_archive_heading_text
). Set the translation preference for that field to Translate. 5. Save the changes and then go to the options page and try updating the translation by switching the language.
If this solution does not resolve your issue or seems irrelevant due to updates or different configurations, 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.
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 further assistance is needed, please open a new support ticket at 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
