Problem: The client was experiencing 404 errors when clicking on author or category links on their website. The URLs showed a duplicated language code (e.g., /enen/ instead of /en/), leading to a 'page not found' error. Solution: The issue was resolved by removing an additional trailing slash "/" from the home URL in the options database table.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Solution: If you're experiencing a missing header menu on your translated pages, we recommend you follow these steps: 1. Open the "menu" template in the default language for editing within WordPress (not in Elementor). 2. Switch to the secondary language using the top admin bar. 3. Click "Edit anyway". 4. Open the template in Elementor for editing. 5. Click on the menu widget. 6. In the settings, select the menu for the secondary language. 7. Save and exit from Elementor. 8. Back in WordPress, click "Open in Translation Editor". 9. Click "Complete" to refresh the translation.
Please note that the client was using outdated versions of the theme and plugins, which can cause issues. We recommend taking a backup before updating them.
Problem: The client is using the theme CarDealer. The Chinese version of the Home Page is displaying a section above the video that should not be there.
Solution: 1. We recommend checking the option that allows hiding the page header on the homepage, as it may not be synchronized with the translated page. 2. Navigate to WPML > Settings > Custom Fields Translation, search for the field
"hide_header_banner"
and set the preference to "Copy". 3. Edit the homepage in English and click on Update to synchronize the field value with the translation on the homepage. 4. The page header should now be hidden on the translated homepage. For more detailed guidance, refer to our documentation on Translating Custom Fields.
If this solution does not seem relevant to your issue, please feel free to open a new support ticket in our support forum.
Problem: The client is using Divi with WPML and is unable to translate buttons created using Divi Grid in the Translation Editor. These buttons are located in the banner area with labels such as LINE UP, DOWNLOADS, QUICK LINKS, and BACK TO ALL EVENTS. Solution: We have corrected the Custom XML configuration for the client. If you're experiencing a similar issue, we recommend you to check and adjust your Custom XML configuration. This can be done by navigating to the WPML > Translation Management page and clicking on the 'Custom XML Configuration' tab. Here's a step-by-step guide: 1. Go to WPML > Translation Management. 2. Click on the 'Custom XML Configuration' tab. 3. Adjust the XML configuration as needed. After these adjustments, the buttons should be available for translation within the Translation Editor.
Problem: The client is experiencing an issue with the WPML String Translation plugin. When the plugin is active, it changes the URL of the product categories in the Woodmart theme. Deactivating the plugin resolves the issue. Solution: We recommend checking the slug for the product categories to ensure it is set correctly. If you need to change the slugs for subcategories, you can do so by navigating to the WooCommerce Multilingual -> Categories tab. Here, you can modify the slugs as needed. If this solution does not seem relevant to your issue, please open a new support ticket with us.
Problem: The client is unable to translate Video link URLs in the Media Carousel widget of Elementor Pro using the Advanced Translation Editor (ATE).
Solution: If you're experiencing issues with translating Video link URLs in the Media Carousel widget when using Elementor Pro, we recommend you try the following steps:
Go to WPML >> Settings > Custom XML Configuration section and add the following code:
Problem: The client was experiencing an issue where the Hebrew menu was covering the entire window instead of displaying correctly like the English version. Solution: We found that the "Speed Optimizer" plugin was preventing the RTL (Right-to-Left) CSS from loading, which is necessary for displaying the Hebrew menu correctly. We recommend deactivating the "Speed Optimizer" plugin to resolve this issue. After deactivating the plugin, please check if the translated menu appears correctly.
Problem: The client is unable to access the translated Dutch homepage at example.com/nl due to a 403 forbidden error. Solution: The site's root directory had a physical 'nl' folder. The issue can be fixed by deleting or renaming the 'nl' folder
If this solution doesn't seem relevant to your situation, please open a new support ticket at WPML support forum.
Problem: The images added with the "Coming Soon Badge" plugin can't be translated with WPML Media Translation. Solution: We recommend switching to the text badge instead of the image badge then trying the following steps after ensuring you have a full backup of your site: 1. Navigate to WooCommerce > Coming Soon config. 2. Change to the text badge for the loop and product page. 3. Translate the text in WPML > String Translation. 4. Edit the file /wp-content/plugins/coming-soon-for-woocommerce/coming-soon-for-woocommerce.php. 5. Replace the code at line 945 from:
$Coming_Soon_WC = new Coming_Soon_WC();
to:
add_action('plugins_loaded', function () {
$Coming_Soon_WC = new Coming_Soon_WC();
}, 999);
This should resolve the issue for the text badge. You can also suggest to the plugin authors to join our Go Global program to ensure better compatibility.
Please note that this solution might be outdated or not applicable to your case. We highly recommend checking the related 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 with us.
Problem: A fatal error occurs on the WPML settings page with the message:
Fatal error: Uncaught InvalidArgumentException: item should be a Collection or an array or an object
. Updating the plugins to the latest version does not resolve the issue. Solution: We recommend taking a complete backup of your site. After ensuring that your site is backed up, please follow the workaround provided in our errata page. You can find the necessary steps to resolve this issue at the following link:
Problem: The client's footer is not being translated by WPML, even though it is set up through the theme customizer. Solution: We recommend translating the footer content using WPML's String Translation feature. If the strings are not visible there, the client should first scan the theme for new strings by navigating to WPML > Theme and Plugin Localization. If there are issues with translating a footer widget, the client can go to Appearance > Widgets and create a separate widget for each language.
For guidance on translating widgets, see our documentation on Translating Widgets,
Problem: If you're experiencing an issue where your menu falls back to its default language when navigating in a language that doesn't have a menu translation, and each menu item is using its original post_title instead of the "Navigation Label" defined in the menu builder, we understand your concern.
Solution: We have identified that this behavior is not a bug but a feature since WPML version 4.5. When a menu is not translated, WPML automatically translates the menu items to the translated post/page titles and links. However, if you prefer to display the original menu with the navigation labels as set in the menu builder, we have a workaround. You can prevent the automatic menu translation by WPML using the code provided in our documentation: Prevent automatic menu translation by WPML when menu not translated in other languages By implementing this code, you will disable the "On The Fly translation" of the menu, allowing the original menu to display.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the workaround does not resolve your issue, 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 do not hesitate to open a new support ticket with us.
In case further help is needed, you can reach out to us on the WPML support forum.
Problem: The client is attempting to delete a secondary language from their website but is encountering an infinite deletion process. They want to have only one language on the website and remove WPML without causing errors. Manually deleting pages, products, and other assets leads to errors on live pages. After a WPML reset, translated files, posts, and pages remain and need to be removed manually. Solution: 1. Ensure that there are at least two languages activated on the site before attempting to delete the secondary language. 2. If the deletion process is infinite, check the debug log for any notices related to WPML that could be causing the issue. For example:
PHP Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /****/test/wp-content/plugins/sitepress-multilingual-cms/classes/API/REST/class-wpml-ate-proxy.php on line 128
3. Perform a full site backup before attempting a WPML reset. 4. After backing up, you can proceed with the WPML reset by following the instructions in this documentation. 5. After a WPML reset, the original posts, taxonomy terms, and media files will not be deleted, only the WPML configuration and translated contents will be cleared.
If this solution does not seem relevant to your situation, please open a new support ticket here.
Problem: The client is experiencing an issue where buttons on their pages point to the correct language version of other pages when translating from English to other languages. However, when adding a Chinese translation first, all multilingual page buttons incorrectly point to the Chinese (zh-hans) pages instead of maintaining the correct language-specific URLs. Solution: We investigated the issue and suspect it might be related to the fact that Chinese uses encoded URLs and Sticky Links. To provide a precise solution, we need to understand the exact steps the client uses to copy a page. We recommend the client to check if they are using any specific method or plugin to duplicate pages and to share that information with us. But in the meantime, the client confirmed that deactivating Sticky Links resolved the issue.
Please note that this solution might be outdated or not applicable to your case. If the problem persists, we encourage you to open a new support ticket. We also 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 further assistance is needed, please contact us on the WPML support forum.
Problem: The client is trying to access the translation of menu items and is inquiring about the support for this feature as of July 2023. Solution: We are currently exploring ways to implement the translation of menu items. Unfortunately, we do not have an estimated timeline for when this feature will be available.
If this solution is not relevant to your case, because it might be outdated or not applicable, we recommend that you open a new support ticket. We also 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 need further assistance, please visit our 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
