Problem: The client has a Dutch website and is translating it into English. They have a custom post type named "medewerkersverhalen" and a shortcode to display these stories. However, when translating an employee story, the English overview page also shows the Dutch stories, which is not intended. Solution: We recommend setting the custom post type to be translatable and to show only translated items. To do this, navigate to WPML -> Settings and set the post type "medewerkersverhalen" to "Translatable - Show only Translated Items".
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 further assistance is needed, please contact us in the WPML support forum.
Problem: If you're experiencing issues with the default language in WordPress settings still being Dutch, and you need it to be in English, including the admin area. Solution: We recommend changing the language of the admin in your profile settings. For detailed instructions, please refer to our guide on Setting the WordPress Administration Language.
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 at WPML support forum.
Problem: The client needed to translate the cart title 'il mio carello' which is set in an Elementor widget added by the jet-blocks plugin.
Solution: We recommended the following steps: 1. Navigate to WPML -> Settings -> Custom XML Configuration and save the following code to register the widget for translation:
2. Go to Templates and search for the template 'Orte Header Webshop'. 3. Edit it using Elementor, make a minor modification to the Italian template (add an empty space, for example, and save it) so WPML recognizes that there's an update available for the translation. 4. Edit the translation of the template, and the item 'il mio carello' should now be available for translation.
After performing these steps, 'il mio carello' should appear as 'my cart' in the English version of the site.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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 for further assistance.
Problem: The client reported that their website was displaying posts in English when clicking the 'load more' button, even though the default language of the page was set to Chinese (zh-hans). Solution: We suggested the client to try a specific solution related to WPML rewriting the .htaccess file, which could potentially resolve the issue of posts loading in the incorrect language. The detailed steps can be found here: WPML Forum Post.
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 WPML 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 experiencing an issue where there appears to be a debt on your accounts for automatic translation services, but you don't see the option to pay the debt. Solution: We have identified that there is an outstanding automatic translation debt for automatic translation credits on your account. To resolve this issue and continue using the Pay-as-you-go services on your site, you need to pay this debt. We sent you a direct link to pay the debt.
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 the issue persists, please open a new support ticket.
Problem: The client was unable to load the Elementor page builder, especially when trying to edit pages in a secondary language. Additionally, the WordPress admin bar was inactive, and there were issues with logging into the site in the secondary language. Solution: 1. We recommended increasing the WordPress memory limit to meet the WPML Minimum Requirements. 2. We suggested updating Elementor Pro to the latest version to resolve compatibility issues. 3. We enabled the "Auto sign-in and sign-out users from all domains" option in WPML -> Languages settings to fix the login issues.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your case, 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. We highly recommend opening a new support ticket if problems persist. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: After copying a site to a new URL and registering it with WPML, the client encountered an error stating 'Translation engines cannot be loaded'. The client attempted to resolve the issue by using the 'Force-enable WPML’s Advanced Translation Editor' button on the WPML Troubleshooting page, but the error persisted due to the browser blocking access to WPML servers. Solution: If you're experiencing a similar issue after migrating your site, we recommend checking the following: 1. Ensure that you selected the correct option in the migration banner that appears in the site's backend after copying/migrating the site. 2. Verify your plugins/server configuration to confirm that there are no firewalls or security rules preventing your site from communicating with our servers.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and ensuring that you have installed the latest versions of themes and plugins. If you still need assistance, please don't hesitate to open a new support ticket in the WPML support forum.
Problem: The client was unable to translate the "Shop" page or have it appear in the Menu sync. Solution: We suspected that the original "Shop" page might have been corrupted. We recommended the client to create a new shop page and check if it works correctly in both languages and with the Menu sync feature.
If you're experiencing a similar issue with translating your "Shop" page or having it appear in the Menu sync, we recommend you try creating a new shop page and testing it in different languages and with the Menu sync.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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.
Problem: 1. The client is using the Woodmart theme and has encountered an issue where there is no option to translate the layout used for displaying a single product. 2. Social network icons in the second language are displayed as 'X', which is due to the special fonts used in the Arabic version of the site. Solution: For the issue with social network icons, we recommend applying custom CSS to assign a different, working font to these icons. Here is an example of how you can do this:
If this does not resolve the issue, we suggest consulting with the theme support to determine which fonts are compatible.
If you find that this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket with us for further assistance. You can do so at our support forum.
Problem: The client was unable to complete translations for certain pages and the main menu in different languages on their multilingual website. They also faced issues with translating images and other media elements. Solution: 1. We advised the client to apply HTML markers to their translated content as per the documentation on Advanced Translation Editor. This should enable them to complete the translations successfully. 2. For translating navigation menus, we recommended following the steps outlined in Translating Menus. 3. To address the issue with image translations, we suggested reading the guide on Media Translation, which provides a detailed process for translating images and other media elements.
If these solutions do not resolve your issues or 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.
Problem: The meta description appears in English on Google. Solution: We recommend checking your meta description and title directly using the tool at https://metatags.io/. If they appear correctly there, the next step is to request Google to re-index your page. This can prompt Google to update their search results with the correct meta information.
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 issue persists, please open a new support ticket.
Problem: The client was experiencing an issue where WPML was stuck refreshing the translation status when translating pages built with Elementor. Solution: We provided a workaround that involves three possible solutions: 1. Turn off Nested Elements in Elementor features. 2. Modify the
file in the Elementor Pro plugin by replacing a specific line of code:
if ( is_checkout() ) {
return;
}
with
if ( is_checkout() || ! WC()->cart ) {
return;
}
3. Install a Must-Use (MU) plugin and add the following code to handle the issue:
<?php
/**
* Plugin Name: WPML PB 470
* Description: Fix PHP Fatal error: Uncaught Error: Call to a member function get_cross_sells()
* Author URI: https://onthegosystems.myjetbrains.com/youtrack/issue/wpmlpb-470
*/
add_filter('wpml_pre_save_pro_translation', function ( $postarr ) {
if (function_exists('wc_load_cart')) {
wc_load_cart();
}
return $postarr;
});
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, 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.
If you need further assistance, please contact us in the WPML support forum.
Problem: If you're experiencing issues where translations work on the desktop version of your site but not on mobile, and certain strings remain untranslated, this might be due to a compatibility issue with the YITH WooCommerce Request a Quote plugin. Solution: We recommend trying the following steps: 1. Open the
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.
Problem: The client needed assistance with translating slug strings for a page, which worked in some languages but not in others. Solution: We recommended that if you're experiencing issues with translating slug strings, you should first try to edit the page in the original language and then switch to the second language to change the page slug. Additionally, we provided a step-by-step guide on how to translate page slugs using the Advanced Translation Editor. You can follow the instructions in our documentation here: Translating Page Slugs.
Please note that this solution might be irrelevant if it's outdated or not applicable to your 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 you still need assistance, please don't hesitate to open a new support ticket in our forum: WPML Support Forum.
Problem: The client is unable to translate a contact form created with the Metform plugin and Elementor widgets on their multilingual site. Solution: A. Translate the form content: 1. Navigate to WPML > Settings > Post Types Translation and set the post type "metform-form" to Translatable. 2. Go to WPML > Settings > Custom XML Configuration and add the following code to translate the form fields:
3. Visit Metform > Forms and translate the form titled "New Form # 1693676945". B. Translate the widget form on the contact page: 1. Follow step 2 above to add a custom XML code to translate the form ID:
2. Switch to the English language in Metform to retrieve the form ID from the URL, which is 2710. 3. Add the following PHP code to the file functions.php in the theme folder to make the number translatable in the Advanced Translation Editor:
4. Update the contact page and its translation. 5. In the Advanced Translation Editor, search for the form ID and translate it. Now, the form should appear translated on the frontend. Refer to the documentation for further details:
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. 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, please visit our support forum 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
