Problem: You are encountering an issue with a red dotted vertical line in the WPML advanced editor, which is preventing you from completing the page translation. This issue arises because certain HTML tags ('sup') are missing in the Portuguese translation. Solution: To resolve this, you need to ensure that the HTML tags in the translation match those in the original content. Specifically, add the 'sup' tags to your translation where necessary. For guidance on handling HTML tags in translations, you can refer to our documentation here: https://wpml.org/faq/what-are-html-tags/ If you wish to use different HTML tags in the translation, consider switching to the WPML Classic Translation Editor. Detailed instructions can be found here: https://wpml.org/documentation/translating-your-contents/using-the-translation-editor/
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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/forum/english-support/.
Problem: The client was unable to add a new language in WPML, which might be due to server-related causes or a compatibility issue with other plugins or the active theme. Solution: We recommend following these steps to identify and resolve the issue: 1. Ensure your server meets the WPML minimum requirements. 2. Test for a compatibility issue: - Create a full website backup. - Disable all plugins except for WPML and its add-ons. - Switch to a default WordPress theme like TwentySeventeen. - Check if the issue persists. - If resolved, reactivate your plugins one by one to identify the problematic plugin. It is advisable to perform these tests in a staging environment if possible.
If the solution provided here does not resolve your issue or seems irrelevant due to being 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.
Problem: The client was unable to add a new language on WPML and opened a support ticket for assistance. Solution: We identified that there was already an open ticket regarding the same issue. We advised the client to follow the existing ticket instead of opening a new one to avoid duplication and potential delays in response. We requested that the client mark the current ticket as resolved and continue monitoring the initially created ticket for updates.
If this solution is not relevant 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing a critical error when trying to activate the WPML Multilingual CMS plugin on their WordPress site, causing the site to crash. Additionally, there is an issue with duplicate plugin versions appearing on the plugin page. Solution: We recommended the client to search for similar issues and solutions on our forums using a custom search URL: here. For the issue of duplicate plugin versions, we advised the client to open a new support ticket as per our support policy of handling one issue per ticket. Regarding the concern about needing to re-translate content after reinstalling the plugin, we assured the client that translations are saved in the database and will not be lost.
If this solution does not resolve your issue or seems irrelevant, 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: The client has installed the WPML plugin on their site and is facing issues with translating the content within the widgets on the homepage. Solution: If you're experiencing issues with translating widget content on your homepage, we recommend following the steps outlined in the WPML documentation. There are multiple methods to translate widgets, but a preferred option is using different widgets for different languages. You can find detailed instructions here: Translating Widgets Guide and specifically for using different widgets for different languages here: Using Different Widgets for Different Languages
If this solution does not resolve your issue or seems outdated, 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. If the problem persists, we highly recommend opening a new support ticket for further assistance at WPML Support Forum.
Problem: After migrating from WP Engine to cPanel, the client experienced issues such as a sluggish dashboard, missing icons, and overall dashboard malfunctions. Clearing the cache did not resolve the issues. Solution: We suggested verifying that the new server meets WPML's minimum requirements, which can be found here: https://wpml.org/home/minimum-requirements/. We recommended using migration plugins like "Duplicator" or "Updraft" for a smoother transition. Documentation for Duplicator is available at https://snapcreek.com/duplicator/docs/, and a tutorial can be viewed here: https://www.youtube.com/watch?v=3YDQ3Ey_2wY. Additionally, we advised clearing any local or server-side caching or CDN that might need to be cleared due to the new server environment.
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 issues with the Advanced Translation Editor (ATE) where previously split fields in product translations are now combined. This change has significantly increased the time required to translate a product. Solution: We confirmed that a new option to keep fields short and separate has been recently introduced and will remain available. This option should help in maintaining the previous efficiency in translating products by keeping fields split as before. If you're experiencing this issue, we recommend checking this setting in your ATE configuration to ensure it's enabled.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are creating an ecommerce site in several languages and have encountered an issue where two texts in the footer are not showing up translated. Solution: We recommend trying the following methods to resolve the translation issue: Method 1: Navigate to WPML > String Translation. At the bottom of the page, there is a checkbox labeled "Look for strings while pages are rendered". Enable this option, visit the front end of a page displaying the untranslated string, and then return to WPML > String Translation to search for the string. Method 2: If the string is not found in WPML > String Translation, it might be categorized as an admin text string. You can follow the process outlined here to find and translate admin text strings: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
If these steps do not resolve your issue, or if the solution 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 https://wpml.org/forums/forum/english-support/ for further assistance.
Problem: You are encountering a PHP notice on your site indicating an issue with trying to get the property 'trid' of a non-object in the WPML plugin. Solution: We recommend following the steps provided in a related support ticket which addressed a similar issue. Please visit the following link to view the detailed steps: WPML support forum post.
If this solution does not resolve your issue or seems irrelevant due to being 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are trying to translate a string from a pop-up plugin, but the string is registered and locked. Solution: The string is locked because the plugin you are using includes an XML file with predefined strings. You can find and translate this string by navigating to WPML > String Translation in your WordPress dashboard. If you're experiencing this issue, we recommend you follow these steps to translate the locked string.
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 here.
Problem: The client is experiencing issues with the translation of tags in a WordPress site using WPML and ACF plugins. Specifically, tags added to media through an ACF field are not synchronizing correctly between the main language (English) and the secondary language (Italian). Solution: 1. Navigate to ACF Field Groups and edit the tags field group. 2. Change the field setting from 'translate' to 'copy'. 3. Go to Media, edit your media in English, make a small adjustment to tags (e.g., remove a tag, refresh the page, and add the tag again). This should synchronize the tags across languages. 4. Replace the existing code in the single.php template with the following code to ensure tags are displayed correctly for the current language context:
// Assuming $image_id is already defined in your template as the ID of the main image.<br />$tag_ids = get_field('tags', $image_id); // Ensure 'tags' is the correct name of your ACF field<br /><br />if ($tag_ids) {<br /> echo '<span class="label-categories label-tags"><b>Tags: </b>';<br /> // Store the tags in an array to ensure uniqueness<br /> $displayed_tags = array();<br /><br /> foreach ($tag_ids as $tag_id) {<br /> // Get the current language<br /> $current_language = apply_filters('wpml_current_language', NULL);<br /><br /> // Get the translated term ID<br /> $translated_tag_id = apply_filters('wpml_object_id', $tag_id, 'post_tag', true, $current_language);<br /><br /> // Get the translated term object<br /> $tag = get_term($translated_tag_id);<br /><br /> if (!is_wp_error($tag) && !in_array($tag->term_id, $displayed_tags)) {<br /> echo '<a href="'. esc_url(get_term_link($tag)) .'" style="margin-right:5px">' . esc_html($tag->name) . '</a> ';<br /> $displayed_tags[] = $tag->term_id; // Add tag to the displayed list<br /> }<br /> }<br /> echo '</span>';<br />}<br />
If this solution does not resolve your issue or seems outdated, 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.
Problem: After updating the site to PHP 8.2, deprecation errors appeared on the front end related to dynamic properties in WPML_LS_Menu_Item. Solution: If you're experiencing similar issues, we recommend disabling the debug mode in WordPress to prevent these warnings from appearing to your visitors. You can do this by editing your wp-config.php file and ensuring it includes the following line:
define('WP_DEBUG_DISPLAY', false);
For more information on handling deprecated errors, please visit:
These notices are expected to be resolved in future updates. 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 needs assistance making the Divi module link URL translatable or linking to its translated pages. The URL does not appear in the WPML Advanced Translation Editor, and there is no option to automatically translate or sync it to its translated page. Solution: If you're experiencing this issue, we recommend searching and translating the link as explained in the following documentation: Translating Links with Advanced Translation Editor. For links to be automatically adjusted to translated ones, they need to be full HTTPS links, and the Divi modules need to be compatible. If you are using third-party Divi modules, they might require additional XML configuration. Please check the following documentation for maintaining Divi Builder compatibility with WPML: Maintaining Divi Builder Compatibility with WPML.
Ultimately, customer was able to fix it by enabling the option "Make themes work multilingual" in WPML -> Languages
Problem: The client is experiencing an error screen when a specific admin tries to log in, which is suspected to be caused by the WPML plugin. Solution: We recommend checking if the affected admin user has their name, surname, and email correctly set up in their wp-admin profile page. Additionally, log in with a different admin account and navigate to WPML -> Translation Management > Translators. Here, verify if the problematic user is set up as a translator and ensure they have at least one language pair assigned.
If this solution does not resolve the 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 for further assistance.
Problem: The client needs assistance with disabling the 'pay as you go' option and removing credit card information from WPML. Solution: If you're experiencing this, we recommend you follow these steps to disable the 'pay as you go' subscription: 1. Navigate to WPML → Translation Management. 2. Click on the Tools tab. 3. In the Pay-as-you-go account details section, click the 'Stop using pay-as-you-go' link. You will receive a final bill for any credits used since your last invoice. Since WPML does not store your credit card information, disabling 'pay as you go' will also remove this information. Payments are processed securely via Stripe.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
