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 was unable to translate a property listing from English into French due to a WordPress caching issue. Solution: If you're experiencing a similar issue where you cannot translate content, we recommend clearing your WordPress cache. After clearing the cache, try translating the content again. This approach resolved the client's issue with translating property listings.
Please note that this solution might be 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 problem persists, please open a new support ticket.
Problem: If you're experiencing issues where the alert element in an Avada form does not inherit the properties of Avada global settings after a successful form submission, it might be due to the theme options not being configured for each language. Solution: We recommend checking your Avada theme options to ensure they are either configured per language or shared across all languages. This is crucial as the Alert element styles likely use Avada Global Options which might not be configured for the English language, causing the form success message to revert to default styling. Please make sure to create a full backup before making any changes. For detailed guidance, visit the following documentation: How to Set Theme Options for Languages in Avada.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is using WPML with Elementor on their multilingual website and wants to replace HTML blocks for different languages on their contact page, rather than translating them. They are unable to find the option to duplicate the page for different languages in Elementor and are concerned about the compatibility of their Elementor-designed pages with WPML's Translation Editor. Solution: We recommend using the manual translation method for the specific page where the HTML blocks need to be replaced. This involves using the WordPress Native Editor to manage translations directly, which allows for different content and designs per language. Here are the steps: 1. Enable manual translation for the specific page by following the instructions here: Using different translation editors for different pages. 2. Watch the video tutorial here: Video tutorial on manual translation with Elementor, which explains how to create and manage separate pages for each language using Elementor and the WordPress native editor.
Please note that this solution might be 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where WPML requests the translation of an entire page after updating a single block on your homepage, this is due to the Advanced Translation Editor (ATE) treating modified content as new because there's no translation memory match for the updated paragraph. Solution:
Since the paragraph content was modified and there is no existing translation memory match for the updated paragraph, the Advanced Translation Editor treats it as new content and requires it to be translated again as a new paragraph. However, the existing translation will still be displayed on the front-end.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client reported that one of the menu items ('Insights') on their website did not translate into Arabic. Additionally, when navigating the Arabic version of the site and clicking on 'من نحن' followed by 'اتصل بنا', it redirected to the English version of the page, despite the pages being translated. Solution: We recommended the following steps to resolve the issue: 1. Navigate to the site backend, then go to Appearance -> Menu. 2. Select the main menu. 3. Use the language switcher in the admin bar to switch to Arabic. 4. Manually translate the 'Insight' string and any other untranslated links. 5. Save the changes.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where a specific block on a page is not showing in the Advanced Translation Editor, despite the text fields being set to translate and appearing correctly on other pages. Solution: We recommend the following steps to resolve the issue: 1. Ensure the post is fully translated using the Advanced Translation Editor. 2. Make a small change to the block content to trigger the 'Needs update' translation icon (circle arrows). 3. Update the translation post again to reflect the changes in the Advanced Translation Editor. Additionally, it appears that caching might be interfering with the display of updated translations. We suggest clearing the WP Engine Cache and then rechecking the block texts in the Advanced Translation Editor.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 the WPML support forum.
Problem: The client faced two issues: 1) The multilingual language switcher was positioned at the bottom of the page instead of the header. 2) Four translated pages did not display their forms correctly, and these forms were not visible in the translation management page. Additionally, there were no updates available, and WordPress support could not resolve the issue. Solution: For the language switcher issue, we added the language switcher block to the Front Page Template. More details on adding language switchers can be found here: Language Switcher Options. Regarding the translation issue, it was due to a block encoded in base24, which WPML could not translate. We resolved this by updating to WPML version 4.9.3 and WPML String Translation version 3.5.2. The client was advised to update these plugins by checking for updates under 'WordPress Dashboard > Plugins > Add new > Commercial (tab)' and then clicking the 'Check for Updates' button. Detailed update instructions are available here: Automated Updates. After updating, the client needed to send the Front Page for translation again and complete the translation process.
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 issues persist, please open a new support ticket at WPML Support Forum.
Problem: The client's live site indicates that it is registered, but the WPML website shows it as not registered. This discrepancy might be preventing updates and causing errors in the settings. Solution: We recommend resetting the site key, which will not affect your current translations. Follow these steps: 1. Log in to wpml.org. 2. Navigate to your account's sites page. 3. Click the trash icon next to the website URL to remove it. 4. In your WordPress Dashboard, go to 'Plugins' > 'Add New' > 'Commercial'. 5. Click 'Unregister WPML' and then 'Register WPML'. 6. Click 'Get a key for this site', copy the auto-generated key, and paste it into the 'Site Key' box. 7. Click 'OK'. For detailed instructions, visit https://wpml.org/faq/install-wpml/#register.
If this solution does not apply to your case, or if it seems outdated, please check the 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 issues persist, we highly recommend opening 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
