Problem: Translated Trips are not shown on the Destination (taxonomy) archive pages. The WP Travel Engine plugin, which declares its compatibility with WPML, is not officially compatible as per our list. Solution: We recommend two workarounds: A. Create Trips in each language without translating the Trip from one language to another using the Language Switcher at the top admin bar. B. Manually translate the Trips by duplicating the Trip from one language to another and then clicking the "Translate Independently" button. For more details on this process, please visit https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/, see section 3.2. Additionally, we suggest contacting WP Travel Engine's support for further assistance and encourage them to join our Go Global Program for official compatibility. Details can be found here: https://wpml.org/documentation/theme-compatibility/go-global-program/. We have also set up a test site to replicate the issue on a fresh WordPress installation. Please install the WP Travel Engine plugin there and check if the issue persists.
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 needed, do not hesitate to open a new support ticket for further assistance.
Problem: The client is using WPML on their site and is unsure why WPML translates row names and images, even though row names are not displayed on the frontend. Solution: We checked the client's website and noticed that some plugins required updating. We recommend updating all plugins to ensure smooth functionality. WPML translates row names to ensure a consistent and comprehensive translation across the entire site, including backend elements that might be used in various contexts. It also translates images to enhance the user experience and improve SEO by providing localized metadata for search engines.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where some customized fields are not appearing in the WPML editor for translation. This problem is possibly related to the field size limitation in the database. Solution: We recommend increasing the field size in the database to accommodate larger data. You can do this by executing the following SQL command:
ALTER TABLE `wp_icl_translate`<br />CHANGE `field_type` `field_type` varchar(264) COLLATE 'utf8mb4_unicode_520_ci' NOT NULL AFTER `timestamp`;
Please ensure to replace `wp_icl_translate` with your actual table prefix and make a backup before applying this change. After updating the database, make a minor edit to the main language page to resynchronize the content.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, 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 experiencing an issue where they receive an error stating 'qEUCHUA is not supported' which prevents automatic translation on their website. Additionally, when clicking on the error, it shows a list of languages without any options to delete or edit.
Solution: If you're encountering the 'qEUCHUA is not supported' error, we recommend mapping Quechua to a supported language in the Automatic Translation Engine. You can find the list of languages supported by the translation engines at https://ate.wpml.org/mt_langs. For more detailed guidance on editing WPML's languages table and using automatic translation with custom languages, please refer to the following documents:
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to see the CTA button on the Chinese version of their website even after adding String Translations in WPML. Solution: We recommended checking the Chinese Language navigation menu to ensure the menu item with the button was appearing, following the 'Fully Custom' method described in this documentation. We then proceeded to translate the menu ID, the button URL, and the button text via the WPML String Translation interface.
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: The client needed a method to translate a large number of categories efficiently. Solution: We recommended translating all taxonomy terms at once by assigning them to a temporary product and then sending it to translation. For more detailed instructions, please visit how to translate all taxonomy terms at once.
If this solution does not apply to your situation, or if it 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client is unable to complete the Arabic translation despite following the correct procedures.
Solution: We have recently implemented some updates that should resolve this issue. We recommend that you check your site again to confirm that the translation is now functioning correctly.
If the problem persists or the solution provided here is outdated or not applicable to your case, please visit our known issues page at https://wpml.org/known-issues/ and ensure you have the latest versions of themes and plugins installed. If necessary, do not hesitate to open a new support ticket for further assistance.
For further support, please contact us through our support forum: WPML Support Forum.
Problem: The client created a mega menu with the basic language set to UK English, which functions correctly. However, in the Dutch version, all menus in the Megamenu are displayed twice. Solution: We recommend applying specific CSS rules targeting the Dutch version to hide the duplicate menu. Here is an example of the CSS code you can use:
Please note that providing custom code support is beyond our usual scope. The code shared above is for demonstration purposes and might help solve the issue. If you need further assistance with custom coding, please consider hiring a certified developer from https://wpml.org/contractors/.
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: If you're experiencing issues where products appear correctly when logged in as an admin but do not appear in incognito mode, it might be due to the products being in draft status or not being automatically published after translation. Solution: First, ensure that the product translation review is complete by following this guide. 1. From the WordPress dashboard, switch to a secondary language using the language switcher on the top bar. 2. Navigate to "Products > All Products." 3. Check if the products are set to 'Published'. If they are in 'Draft', open the product in the Editor, go to the Publish meta section, change the status to "Published," and click on 'Update'. Additionally, check the WPML > Settings and ensure the option to 'Publish the post translations' is selected. This setting will ensure that translations are published immediately upon completion. For any products currently saved as drafts, you will need to publish them manually.
If this solution does not resolve your issue or seems irrelevant due to outdated information or a different case scenario, we recommend opening a new support ticket. We also advise 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 reported an issue with mixed content warnings on their website using the WPML plugin. The warnings were related to HTTP resources being loaded instead of HTTPS, specifically flag icons. Solution: We discovered the issue was due to a conflict between the lazy loading script enabled in both the Theme settings and the WP Rocket plugin. To resolve this, we disabled lazy loading in both settings, then re-enabled it only in the Theme settings and resaved the permalink structure. This adjustment ensured that the flag icons loaded correctly over HTTPS without recurring issues.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 at WPML Support Forum.
Problem: If you're experiencing a memory size error when updating a post with a significant number of ACF fields using Advanced Custom Fields Multilingual, and the issue does not occur when the plugin is deactivated, it might be due to database corruption. Solution: We recommend taking a full backup of your site and then checking the database for any inconsistencies or corruption. In this specific case, the issue was traced back to a corrupted entry in the 'postmeta' table for the file field 'installation_manual' in the 'Post type - Product' field group. Deleting the corrupted entries and re-updating the product resolved the issue.
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.
Problem: If you're experiencing an error with ACFML when saving or viewing a post in the WordPress admin, where
$fieldParent
can sometimes be null, leading to a PHP warning on line 249 of class-wpml-acf-repeater-shuffle.php, this summary is for you. Solution: We recommend trying the workaround provided in the following documentation: ACFML PHP Warning: Attempt to read property 'post_content' on null. Please ensure to back up your database before making any 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are trying to translate a post using WPML, but the translation option is not visible in the backend. Both original and translated posts are listed together instead of being separated as translations. Solution: We recommend ensuring that your Posts are set as translatable in WPML. You can do this by navigating to WPML → Settings → Post Types Translation. For more detailed guidance, please visit Translating Custom Posts.
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: If you're experiencing issues where the links on buttons on your site always load in Bulgarian, regardless of the language you are in, and you're wondering if you need to manually set the links for each language separately. Solution: First, we recommend editing the links in the main language to be relative instead of absolute. For example, change the link from 'https://example.com/product-category/product/' to '/product-category/product/'. Save the page in the main language, then edit and save the translations without changing anything. This should allow WPML to automatically adjust the links for each language.
If the issue persists, it might be due to the links being encoded, which prevents WPML from auto-adjusting them. In this case, follow these steps: 1. Go to WPML -> Settings -> Custom XML configuration and add the following code:
2. Edit the file: wp-content/plugins/sitepress-multilingual-cms/inc/absolute-links/absolute-links.class.php in the method: \AbsoluteLinks::_process_generic_text right after:
After applying these changes, make a minor edit to the home page and save all translations as they are. This should correct the URL issues in secondary languages.
If this solution does not resolve your issue, or if it seems 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
