Problem: The client is trying to translate a Woocommerce coupon on their website. Solution: We recommend not setting coupons as translatable because they are unique for each shop and not based on language. However, if you decide to translate them, you should go to WPML -> Settings -> Post Type Translation and change the coupons' translation preference.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also highly recommend checking related known issues here, 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 has translated their website into Polish, but the Polish shop page is not functioning correctly, while the regular shop page works fine. They are using the Divi theme with WooCommerce. Solution: If you're experiencing issues with your Polish shop page not functioning correctly while using Divi and WooCommerce, it's essential to ensure that the WooCommerce Multilingual & Multicurrency plugin is active and properly configured. This plugin is crucial for the WPML to work correctly with WooCommerce. We recommend reading and following our guide on setting up WooCommerce Multilingual & Multicurrency, which you can find here: https://wpml.org/documentation/related-projects/woocommerce-multilingual/.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please do not hesitate to 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: After upgrading to PHP 8.3.x, you are encountering a PHP Deprecation notice on Toolset Types 3.5.2. The notice indicates that the return type of OTGSToolsetCommonUtilsRecursiveDotFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[ReturnTypeWillChange] attribute should be used to temporarily suppress the notice. Solution: We recommend disabling the debug mode in WordPress to prevent these warnings from being displayed to your visitors. This can be achieved by editing your wp-config.php file and ensuring it includes the following line:
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. If needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing issues with the WPML plugin on their website. The pages were barely translated, and the layout was disrupted. Additionally, there was a database error indicating a missing table: 'cuorehub_WPQ6E.staging_yBB_icl_strings'. Solution: We resolved the issue by making adjustments in the WPML settings and editing the pages: 1. Navigate to WPML-> Settings-> Custom Fields Translation section. 2. Set the "mfn-page-items" field to "Translate". 3. Save the changes. 4. Edit the page in the default language. 5. Add 'V2' to the title and update the page. 6. Remove the 'V2' and update the page again. 7. Update the translation. We advised the client to apply steps 4 to 7 for each page to ensure proper translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly 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 developing a site using Elementor with WPML and want to auto-translate links in Elementor icon list items. Despite setting a glossary for the link and resending the page to auto translation, the link remains untranslated. Solution: 1. First, edit the translation of the page. In the Advanced Translation Editor (ATE), use the search option at the top left to find the URL. You can search for the entire URL or just a part of it. For more details, see Translating links with Advanced Translation Editor. 2. If the above step does not resolve the issue, follow these steps: - Go to WPML -> Settings -> Custom XML Configuration tab and paste the following code:
- Press the Save button. - Modify the original page slightly and press the Update button. - Update the translation via WPML's Advanced Translation Editor. - Re-open the translated page to check if the links are now translated.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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, please visit our support forum at WPML support forum.
Problem: The client was unable to translate certain texts into Arabic, including the word 'SHOP' and phrases in the top bar of their website. Additionally, Arabic characters in the Slider Revolution were displaying backwards and separated. Solution: For the Slider Revolution issue, we recommended accessing WP Admin -> Slider Revolution and editing the 'Demo-rtl 1' slider used for Arabic. The client should remove the text layers and add them again without applying animation effects that break the words into individual letters. For the text in the top bar, which is managed by the 'Thim Elementor Kit' plugin (not WPML-compatible), we attempted standard methods to find the text through string translation but were unsuccessful. We offered to download a clone/snapshot of the website to further investigate how the plugin manages this text. For the image accordion issue, we made the fields translatable by adding custom XML configuration to the WPML settings. The client should open the page in the default language, make a minor edit to refresh the elements detected by WPML, and then proceed with 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: You are trying to add the site key in the OTGS installer but cannot register the key. Solution: If you're experiencing this issue, we recommend you first go to your WPML.org account profile and remove the key generated for the site you are attempting to register. Then, navigate to Plugins->Add new->Commercial tab in your WordPress admin. Here, either unregister WPML or register WPML and click on "Get a key for this site". This action will automatically generate a new key code for your site.
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 issue persists, please open a new support ticket.
Problem: You are trying to remove all remnants of the RankMath plugin from your WPML translations after switching to Yoast, but despite deleting the plugin, its remnants still appear in WPML translations. Solution: The remnants of RankMath are still present in your database, which is why WPML continues to offer these fields for translation. To completely remove these remnants, follow the steps similar to those used for removing old custom fields from Yoast, which can be found in our forum discussion: https://wpml.org/forums/topic/split-how-can-i-remove-old-unused-custom-fields/ and https://wpml.org/forums/topic/delete-used-fields/. Make sure to search for 'Rank Math' fields specifically when prompted for the field name. It is crucial to create a backup of your database before proceeding with the removal.
If this solution does not apply to your case, or if it seems outdated, 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: https://wpml.org/forums/forum/english-support/.
Problem: When activating 'WooCommerce Multilingual & Multicurrency', the website fails to display anything after adding an item to the shopping cart. The client suspects it might be due to a lack of translation on the account page and unapplied endpoints. Solution: 1. Enable WP_DEBUG in the wp-config.php file to log errors. Add the following lines:
2. Increase the WP Memory Limit to at least 256M as described here: Increasing WP Memory Limit 3. If the issue persists, provide temporary access to your site for further investigation, ensuring you have backed up your site. 4. Check for theme conflicts, particularly with the theme's core plugin. A similar issue was resolved in this thread: WPML Forum: Theme Conflict
If these steps do not resolve your issue, or if the solution becomes outdated, please visit WPML Known Issues to check for related issues. Ensure you have the latest versions of themes and plugins installed. If the problem persists, we recommend opening a new support ticket at WPML Support Forum.
Problem: The client is experiencing issues with multiple copies of each product after deactivating the WPML plugin and is seeking a way to offboard from WPML without manually deleting all the content. Additionally, the client is inquiring about the process for obtaining a refund after the designated period for automatic refunds has passed. Solution: If you're experiencing issues with residual translated content after deactivating WPML, we recommend performing a WPML reset to remove all translated content and WPML settings. Please follow the detailed steps provided in our documentation: Deleting Languages and Plugin Data by Doing a WPML Reset on Your Site. Regarding the refund, if you have already sent a refund request, our Accounts team will handle it as we do not have access to account-related tasks. For further inquiries or if the refund period has passed, please contact the Accounts department directly at hello@wpml.org.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where adding a WooCommerce shortcode breaks the page editing functionality, and you're unable to edit the page until you disable either WPML or WooCommerce plugins, the problem might be related to string translations. Solution: We recommend checking the WPML -> String Translation section for the specific string 'Select options for'. It's likely that the translation format is incorrect. You should change it from "%": Déan rogha to "%s": Déan rogha. This adjustment has been tested and should resolve the issue.
Regarding the removal of all current strings and using only .mo files, we advise against deleting strings from the String Translation as this will result in strings appearing untranslated. It's essential to have them registered within the String Translation screen for proper functionality.
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 wants to use the same translations for domain.at as domain.de without translating all content twice for Austria and Germany, both speaking German. Solution: We recommend creating 'at_AT' as a custom language. This allows you to use our fallback method, where content will display in the original language if no translation is available, and also generate a translated permalink. You can set up the multi-domain configuration as described in the following documentation:
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.
Problem: After changing the default language from Italian to English on a bilingual website, the availability calendars stopped functioning. Solution: We recommend two potential solutions: 1) Modify the database: - Access your database manager, such as PhpMyAdmin. - Execute the following SQL query:
SELECT * FROM `wp_postmeta` WHERE `meta_key` LIKE '%room_type_id%'
- Replace the IDs as necessary based on your results. 2) Create new content in the English language: - Develop a new accommodation type for the English version. - Add accommodations and configure rates for this new type. You may need to remove the old Accommodation Types and Rates.
If these steps do not resolve your issue or if the solution 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.
Problem: The client accidentally deleted a production site key in WPML and encountered an error when trying to add a new site key, with the system reporting that the key doesn't match. Solution: If you're experiencing this issue, we recommend that you unregister your website and then register it again with the new site key. This should resolve the problem. You can find a step-by-step guide on how to unregister your website here.
Please note that this solution might be irrelevant if it's 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 issue persists, please open a new support ticket.
Problem: The client is using the 'WooCommerce Product Tabs' plugin and is unable to find the new string for product tab titles in WPML > String Translation. Additionally, many 'WooCommerce Product Tabs' strings are marked as 'pending with the hourglass' and are not appearing elsewhere. Solution: We recommend following these steps to resolve the issue: 1- Go to Products -> Product Tabs and access the trash (or click the link to your trash directory). 2- Delete the French product tabs. 3- Open the file .../wp-content/plugins/woocommerce-product-tabs/src/Product_Tabs.php. 4- Locate line 60 and replace the code:
5- Go to WPML > String Translation, enable the option 'look for strings while pages are rendered' at the bottom of the page, and visit a product with the tabs so WPML includes the new strings. 6- Go to WPML > String Translation, search for the tabs titles, and translate them.
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 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
