Problem: WordFence is reporting some WPML plugins as abandoned.
Solution: If you're experiencing false notices from WordFence about WPML plugins being abandoned, we recommend you to ignore these notices and continue using the plugins.
Problem: The client is experiencing issues with the Contact Form 7 plugin not working in the English version of their website, despite being correctly translated with WPML. The form is supposed to connect to the GetResponse Email Marketing System via the Bit Integrations plugin. Solution: We recommend taking the following steps to troubleshoot the issue: 1. Ensure you have a full backup of your website and database. 2. Update WordPress to the latest version and check if the issue persists. 3. Deactivate all plugins except for WPML, Contact Form 7, and the Contact Form 7 multilingual addon, then test the form again. If the form works without the Bit Integrations plugin, it suggests that the issue may be with the Bit Integrations plugin, which is not on our compatibility list. In this case, we advise contacting the support for the Bit Integrations plugin. Additionally, plugin authors can join the WPML’s Go Global program to ensure compatibility.
If this solution does not seem relevant to your situation, please open a new support ticket in the WPML support forum.
Problem: The client is trying to translate checkout fields on their website. Some fields are translatable, but others are not found despite trying various solutions. Solution: We recommend translating the strings in the
woo-checkout-field-editor-pro
text-domain. After updating the translations, the client should verify the fields on the front end. If this solution doesn't seem relevant, please open a new support ticket with us.
Problem:
The client has a multisite setup with subdomains and is facing issues with English pages not appearing as translated from French, even though they have been uploaded to the subdomains.
Solution:
You can connect the English pages as translations of the French pages by following this guide:
Problem: The client added a language switcher to the website menu from the backend at WPML > Languages > Menu Language Switcher, but it was not appearing on the website's frontend. Solution: We added the Menu Language Switcher from the WPML > Languages page and noticed it appeared correctly when logged in but not in a private browser. We resolved the issue by clearing the cache, which made the language switcher display correctly on the frontend.
Problem: The client used WPML's Automatic Menus Sync and noticed that the English "Home" menu item shows an error that the translation doesn't exist. The page was already translated and the translation is accessible. Solution: The Homepage menu item points to an untranslated page in the default menu. It was fixed with the following steps: 1. Remove the current "Home" item from the menu. 2. Add the correct homepage to the menu. 3. Rerun the menu synchronization process. If this solution does not seem relevant to your issue, please feel free to open a new support ticket with us.
Problem: If you're experiencing a warning about an undefined property in WooCommerce related to payment gateways on your site, specifically 'WooCommerce::$payment_gateways' in 'class-wc-subscriptions-cart.php'. Solution: We recommend updating to the latest version of WooCommerce Multilingual (WCML), which is 5.3.2. After updating, please try the following workaround:
Visit the errata page . Our developers are working on a permanent fix.
If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket with us for further assistance. You can do so by visiting the WPML support forum.
Problem: The client's website supports eight languages, with English as the main language. All languages were translated using WPML, but only the Chinese language links were showing a 'no result' error message. The client tried removing and re-adding the Chinese language, making small changes, and using the 'Translate Link Targets' option in WPML settings, but the issue persisted. The client also noted that the same process worked fine for another post the previous day.
Solution: 1. We identified that the issue was due to the Chinese version of the product being set to redirect to another product that was unavailable. This redirection was configured by the Yoast SEO plugin. 2. We advised the client to go to Yoast SEO > Redirects and delete the redirect if it was found there. Alternatively, the client could reach out to the Yoast Support team for assistance in removing the redirect. 3. After the client's update, we confirmed that the page was loading correctly. We recommended clearing the caches from the site and browser, and also from the server level if applicable, to ensure the changes take effect.
If this solution doesn't look relevant to your issue, please feel free to open a new support ticket with us.
Problem: After installing the WPML Multilingual CMS plugin, the site admin panel stops working and displays a critical error. The error message indicates that the class 'DOMDocument' is not found, which is part of a PHP extension that may not be enabled on the server. Solution: If you're experiencing a critical error after installing the WPML Multilingual CMS plugin and the error message mentions that the 'DOMDocument' class is not found, we recommend checking if the PHP XML extension is enabled on your server, as the 'DOMDocument' class is part of this extension. A similar issue was resolved by another client, and you can follow the steps provided in this thread: https://wpml.org/forums/topic/fatal-error-when-trying-to-access-installed-plugin/#post-12615561.
Problem: The client wants to remove the WPML plugin and needs to know where the translated words or strings are located on the website to ensure the removal does not crash the site.
Solution: If you're looking to remove the WPML plugin and want to identify the translated strings, we recommend checking the WPML -> String Translation section. You can delete strings from there by following this guide: How to delete a string.
For translated pages and posts, you can find all translations under the Pages and Posts sections in your WordPress dashboard. Make sure to switch to the secondary language(s) to view and remove the translations. It's also important to remove them from the Trash to ensure they are completely deleted. Detailed instructions can be found here: How to delete the translation of a page.
If you wish to completely remove all translations, added languages, and all data added by WPML from the database and files, please consult the following guides:
Problem: The client wants to shorten the language names in the default language switcher to display as 'EN' for English and 'FR' for French instead of the full language names. Solution: We recommend creating a full backup of your website first. Then, navigate to WPML > Languages > Edit Languages. Here, you can edit the values in the "Translation" column by replacing the full language name with the language code (e.g., 'EN' for English, 'FR' for French).
Please be aware that these changes will affect all the language switchers on your site.
Problem: The client is using Themeco X with Cornerstone as the builder for a training system using Learndash. They have scanned the Pro theme for strings but cannot find them to translate. Pages built with Cornerstone do not show translations. Solution: If you're experiencing issues with translations not appearing on pages built with Cornerstone, we recommend checking the following Errata page for a known issue and its workaround:
Please try the workaround mentioned on the Errata page. If the problem persists, provide us with the link to the page where the issue occurs and the specific content you're trying to translate, so we can further investigate.
If this solution doesn't look relevant to your issue, please open a new support ticket at WPML support forum.
Problem: The client is trying to display the language selector in the mobile menu of their DIVI theme website in one line, instead of stacked vertically like the other menu items.
Solution: We attempted to resolve the issue with custom CSS code. However, due to a significant amount of custom coding from the theme or one of the active plugins, the default WPML CSS properties were being overwritten, preventing the language selector from aligning horizontally in the mobile menu. We provided the following custom CSS code, but it did not achieve the desired result:
Since the custom CSS did not resolve the issue, we recommend hiring a front-end developer or a WPML contractor to perform the necessary custom work. Our colleagues also confirmed that custom work is required due to interference from other custom codes.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is trying to translate a string under the Flatsome theme settings. Solution: We recommend following the steps for "Translating Admin and Settings Strings" as outlined in our documentation. You can find the guide here: Translating Admin and Settings Strings.
Additionally, we noticed that the PHP 'WP Memory Limit' is below the required 128MB or recommended 256MB. We advise contacting your hosting provider to increase this PHP value. Furthermore, ensure that your MySQL version is updated to 5.6 or higher, as per our minimum requirements, which you can review here: WPML Minimum Requirements.
If this solution doesn't look relevant to your issue, please open a new support ticket in our forum: WPML Support Forum.
Problem: The client is concerned about the high cost of translating their website, which includes 19,079 products, 500 blogs, and additional pages, into 5-6 main languages using WPML's automatic translation services. The client's budget is 3-4K Euro, but the estimated cost is around 9-10K Euro. Solution: We recommend reviewing two existing support tickets that might provide useful information on managing translation costs:
We also suggest considering the "pay as you go" membership as the most cost-effective option for automatic translation. You can find more information here: How to sign up for pay as you go
Manual translation is not recommended due to the vast amount of content and the time it would require. We understand the budget constraints and recommend starting with translating a few products to see how it goes and then continue as the budget allows. Unfortunately, there are no other packages or alternatives that would significantly reduce the cost due to the volume of content that needs translation.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
