Problem: The client reported that the floating language switcher was not visible on their website, even though the theme author had confirmed that the issue was fixed on their side. Solution: We first asked the client to ensure that they had implemented the floating language switcher as per our documentation: Custom Language Switcher. After verifying that the implementation was incorrect, we installed a custom code plugin to safely add the necessary code without modifying the theme files directly. We then corrected the CSS for the floating language switcher to ensure it displayed correctly with the theme. The client can now see the floating language switcher and can customize its appearance through
Appearance > Custom CSS
.
If this solution does not resolve your issue, or if it seems outdated, we recommend checking the 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 is unable to translate a section of their website, specifically a custom post type such as 'Portfolio' or 'past events', because the edit translation icon/page is not available. Solution: If you're experiencing this issue, it may be because the custom post type is not set as translatable. We recommend enabling translation for it. Please follow the guide on how to do this here: Translating Custom Posts. Additionally, we have enabled debug information for this support ticket. You can follow the instructions to retrieve and share it with us here: Provide Debug Information.
If the solution provided here is not relevant to your case, either because it’s outdated or not applicable, 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: The client is using the Woodmart theme on a product page with HTML blocks inside tabs, which are not displayed in translated products. Additionally, the content of some tabs isn't being translated. Solution: 1. Ensure that the HTML Blocks themselves are translated. If they are and the issue persists, consider rebuilding the content using regular Elementor widgets/sections and then translate it normally with WPML. This approach is recommended for better compatibility. 2. If preferring to keep the current setup, manually edit and adjust the translated HTML Blocks for each language. More information on the manual approach can be found here: Using different translation editors for different pages. 3. Check if tabs/custom fields are set as translatable in WPML settings. Go to WPML > Settings > Custom Fields Translation and set the related fields to “Translate”. After setting this, complete the translation to 100%, and save it. This should resolve the issue with missing tabs and content on translated product pages.
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: You are facing an issue where some WooCommerce products exist in French, Dutch, German, and Swedish, but the English translation is missing. Despite using WPML Advanced Translation Editor (ATE) to create the English translation, it does not appear in WooCommerce, and the translation job remains 'In progress'.
Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to: WordPress Dashboard → WPML → Support → Troubleshooting. 2. Execute these options: - Clear the cache in WPML - Remove ghost entries from the translation tables - Fix element_type collation - Fix WPML tables collation - Assign translation status to duplicated content - Set language information - Fix post type assignment for translations - Synchronize local job IDs with ATE jobs - Synchronize translators and translation managers with ATE - Retry stuck automatic translations 3. After completing the above, go to: WordPress Dashboard → WPML → Translation Dashboard → Jobs. Cancel any pending or stuck jobs, and attempt the translation again. If the English product was the original and is now missing, consider restoring the database from a backup taken before the issue occurred. If the original product still exists but is no longer linked to its translations, you can reconnect them by following this guide: https://wpml.org/faq/how-to-link-already-translated-pages/
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 for further assistance.
Problem: The client is experiencing issues with the translations of tickets in an event calendar setup, where tickets appear in the German version but not in the English version. Solution: We recommend following the steps outlined in the documentation for integrating WPML with the Events Calendar to ensure proper localization and translation of event tickets. You can find the guide here: Events Calendar Localization with WPML. Additionally, there is a known issue with Event Tickets Plus where translated events do not display tickets correctly. Please follow the specific steps provided in the WPML errata page here: Event Tickets Plus Translated Events Issue. If these solutions do not resolve your issue, or if they seem outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Also, ensure you have the latest versions of your themes and plugins installed, and check for related known issues at WPML Known Issues. For further assistance, please contact us through the WPML support forum.
Problem: The client experienced multiple issues after migrating their website and changing themes, including posts and media not being displayed, and a critical error occurring when accessing certain WPML features. Solution: 1. We recommended creating a backup of the website or using a staging site to avoid disrupting the live site. For the posts not showing: - Navigate to WordPress Dashboard > WPML > Support > Troubleshooting and click the Set Language Information button. For media not showing: - Go to WordPress Dashboard > WPML > Settings > Media Translation, ensure all checkboxes are enabled, and click the Start button. For the critical error: - Edit the
If these steps do not resolve the issues, or if the solution becomes 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 for further assistance.
Problem: The client reported a critical error on their website in the German language version, specifically mentioning issues with deprecated functions and a fatal error related to the Uncode Core plugin and incorrect string translations. Solution: 1. We advised the client to enable debug mode by adding the following code to their
For more information on debugging, visit https://wpml.org/documentation/support/debugging-wpml/. 2. After receiving the debug information, we identified that the issue was due to incorrect string translations in WPML String Translation. The client was instructed to deactivate the Uncode Core plugin temporarily, search for strings containing '%s' or '%c', and correct the translations where only '%' was present without the accompanying character. 3. We confirmed the fix after the client adjusted the translations and verified that the error was resolved.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is unable to translate page content built with Pro/Cornerstone and ACF using WPML, despite following initial plugin guidelines. Only menus, page titles, and Gravity forms are translated, while the main content and ACF custom post types (News, Case studies, Products) remain untranslated.
Solution: 1. Ensure that the WPML settings for custom fields and post types are correctly configured: - Navigate to WPML -> Settings and locate the Custom Field Translation section. Set Pro/Cornerstone related fields (look for prefixes like '_cornerstone_', '_cs_') and ACF fields to Translate. - In the Post Types Translation section, ensure that the custom post types are set to Translatable. 2. Use the WPML Translation Dashboard to send content for translation. 3. If issues persist, apply the workaround provided in the WPML errata for Pro Theme layout texts not being translatable via WPML translation editor: https://wpml.org/errata/pro-theme-layout-texts-not-translatable-via-wpml-translation-editor/ 4. Increase the WordPress memory limit to at least 256MB as described here: https://wpml.org/home/minimum-requirements/
If these steps do not resolve the issue, 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 for further assistance.
Problem: The client was unable to access the WPML > Translations page, and the translation queue was not loading correctly, showing around 18,000 pending translation jobs. Additionally, there was an issue with adding new WooCommerce product categories, which resulted in an 'Empty Term' error even with simple category names/slugs. Solution: We addressed the translation queue issue by opening a new support ticket specifically for that problem to keep the discussion focused and clear. For the WooCommerce product category issue, we recommended checking the WPML taxonomy/term tables and WooCommerce product_cat language data as the creation of product categories seemed to be blocked or corrupted by taxonomy/language handling. We also suggested disabling certain plugins and performing WPML troubleshooting actions such as setting language information, fixing terms count, synchronizing post taxonomies, and clearing the WPML cache.
If you're experiencing similar issues, we recommend trying the steps mentioned above and ensuring that all plugins and themes are updated to their latest versions. For detailed guidance, you can check the related known issues at https://wpml.org/known-issues/. If the problem persists or if the solution provided here becomes outdated or irrelevant to your case, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You want to translate post content but keep the post slug in the default language (English). Solution: We recommend following these steps: 1. Navigate to
WPML > Settings > Translate documents options
and enable Copy from original language if translation language uses encoded URLs. 2. Go to
WPML > Languages > Edit languages
, select Encode URLs: Yes. 3. Save all changes. 4. Edit a post, make a small change to the content, update it, and then translate it again. Check the translation post slug in the frontend. For more details, please read our documentation on translating page slugs: Translating Page Slugs 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 you still need assistance, please open a new support ticket at WPML Support Forum.
Problem: The client is experiencing an issue where the translated WooCommerce product base slugs are not correctly applied to single product URLs in a multilingual WooCommerce + WPML staging site. Despite correct settings in WPML and WooCommerce Multilingual, the German single product URLs still use the Dutch product base instead of the translated German base. Solution: We recommended the client to ensure that the option 'Set different slugs in different languages for Products' is enabled in WPML > Settings > Post Types Translation. After enabling this setting, it's crucial to save the base slugs for different languages and then save the changes. Additionally, the client should navigate to WP Dashboard > Settings > Permalinks and save the settings there to clear the permalinks cache. This action should resolve the issue with incorrect URL slugs.
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. Please 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, you can contact us directly through our support forum at WPML support forum.
Problem: You are unable to edit the link in the WPML editor. Solution: We recommend trying to unlock the URL for editing. Please follow the steps shown in the screenshot provided by our support team. If this solution does not resolve your issue or seems outdated, we encourage you 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.
If you need further assistance, please contact us through the WPML support forum.
Problem: The Add to Cart button was not functioning in a secondary language on a WooCommerce site using the Woodmart theme and WPML. The button was unresponsive or just spinning infinitely, specifically in the Romanian language, while it worked correctly in other languages. Solution: 1. Ensure all WPML-related plugins are updated to the latest versions: - WPML Multilingual CMS - WPML Media Translation - WPML String Translation 2. Clear all caches including browser, WordPress, and theme-specific caches after updating. 3. Check for JavaScript or PHP errors on the secondary language product pages. 4. Review WPML and WooCommerce compatibility with the Woodmart theme for issues specific to secondary languages. 5. Inspect and correct any incorrect string translations in WPML -> String Translation, particularly those related to WooCommerce functionalities.
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.
Problem: The client is using the Houzez theme with WPML for a multilingual real estate website and faces issues with property synchronization and translations. Specifically, properties created in a translated language do not appear in the default English version. Additionally, there are concerns about the over-translation of admin texts potentially affecting theme options.
Solution: We confirmed that the Houzez theme is compatible with WPML and no additional plugins are needed. For the main issue of property titles not updating across languages, we provided two solutions: 1. Translate directly from the property edit screen: - Navigate to Real Estate → Properties. - Edit the property and use the gear icon to open the translation in the Advanced Translation Editor. - Complete and save the translation. 2. Use the WPML Translation Dashboard: - Go to WPML → Translation Dashboard. - Select the property and send it for automatic translation, then review and complete.
For the workflow where English and Hungarian content are manually included in the same property, we advised against this practice. Instead, properties should be created in one language and then translated into another using either the Advanced Translation Editor or by disabling it and using the WordPress editor. This ensures proper structure and synchronization across languages.
If these solutions do not resolve the issues or if they 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client reached out regarding an unexpected annual subscription charge for a service no longer in use, due to an inactive key/account. The charge occurred because the employee managing the service left without informing the team of the active subscription. Solution: We explained that we offer a 30-day money-back guarantee for the initial purchase of WPML, but this does not apply to subscription renewals after this period. Therefore, a refund for the renewal charge is not available. We recommended that if the client prefers to manage renewals manually to avoid future issues, they should disable automatic renewal by following this guide: https://wpml.org/faq/cancel-wpml-subscription/
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 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
