Problem: The client is experiencing intermittent 404 errors when switching languages on their website using WPML. The posts are correctly translated and published, and the issue is not consistent. Troubleshooting steps already taken include verifying translations, checking permalink settings, clearing cache, disabling caching mechanisms, disabling other plugins, and using WPML troubleshooting options.
Solution: We recommended checking if the slug for the post/page where the issue occurs has been used for any other post/page/post type in the same language, as WordPress requires unique slugs for each item. We also suggested that caching rules might be causing the issue by serving a cached 404 error version of the page. We asked the client to share the link to the page for further examination and inquired about a plugin called "Custom Post Type Permalinks" that could be modifying permalinks, suggesting to disable it or check any changes made with it.
Please note that the solution provided might be 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: The client had an issue where product names on a tag archive page were not displaying in the correct language, despite the products being translated. When switching to another language, the product names remained in English, although the individual product pages were correctly translated.
Solution: 1. We accessed the page edit screen containing the product listing shortcode. 2. We used the top admin language switcher to switch the language to Estonian. 3. We updated the shortcode to use the correct Estonian slug for the category, for example:
4. We saved the changes, which resolved the issue for the Estonian language. 5. We repeated the process for the Russian language, updating the shortcode with the Russian slug:
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we 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 problem persists, please open a new support ticket with us.
Problem: The client needed to delete posts that had been translated but not duplicated and wanted to recreate the translations for those pages. Solution: We recommended the following steps after ensuring a full site backup is in place: 1) Navigate to Posts>>All Posts in the WordPress dashboard. 2) Switch to the Hebrew language using the dashboard language switcher at the top header. 3) Delete the Hebrew posts. 4) Click on the Trash link. 5) Permanently delete the posts from the trash. Additionally, we provided a direct link to manage the Hebrew posts: https://www.siteurl.com/wp-admin/edit.php?post_type=post&lang=he
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, 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 in the WPML support forum.
Problem: The client was unable to access the admin menu to delete old second language data due to a conflict between TranslatePress and WPML databases, which resulted in a redirection issue and a broken page error. Solution: We recommended the following steps to resolve the issue: 1) Deactivate all other plugins and switch to a default theme, such as Twenty Twenty-Four. 2) Activate WPML. 3) Navigate to WPML > Support > Troubleshooting page. 4) Select the 'I am about to reset all translation and language data' option. 5) Click on the 'Reset and deactivate WPML' button. 6) Go to WPML > Setup. 7) Configure WPML with English as the default language and Hebrew as the secondary language. 8) Reactivate plugins in groups of 4-5. 9) Switch back to the original theme.
Please note that this solution might not be relevant 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 necessary, please open a new support ticket in the WPML support forum.
Problem: The client is experiencing CSS errors after migrating a WordPress site from a development environment using NginX to a UAT environment using Apache. The issue occurs when the 'WPML Multilingual CMS' plugin is activated, causing CSS paths to point to localhost.
After migration, if the issue persists, try the following troubleshooting options in WPML → Settings → Troubleshooting:
Clear the cache in WPML
Remove ghost entries from the translation tables
Update the domain name in the language switcher settings
Always remember to back up your database before updating.
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 our support forum.
Problem: The client was experiencing an issue where the German logo was still displaying on the English version of the site, even after clearing the cache.
Solution: We recommended the following steps to resolve the issue: 1. Remove and re-add the logo from the Cornerstone >> Theme Options page. 2. Go to Media >> Library, search for the logo image name to find its ID. 3. Go to the Admin strings translation page, search for the logo ID, and enable its translation. 4. Go to WPML >> String Translation and add the English logo image ID as the translation.
After following these steps, the correct logo should display for each language.
If this solution does not apply to your situation, or if it seems outdated, 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 do not hesitate to open a new support ticket.
Problem: The client is experiencing issues with the site key not working.
Solution: If you're encountering a similar problem with your site key, it's important to ensure that you have registered your site with the correct domain. Domains with and without 'www' are considered different. We recommend registering your site using the exact domain that you are using. For guidance on how to register your site, please refer to our documentation: https://wpml.org/faq/install-wpml/#register.
If this solution does not apply to your case, or if it's 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 further assistance is needed, please contact us in the WPML support forum.
Problem: The client experienced a noticeable slowdown and layout issues with Elementor after installing WPML. Elements such as headers and footers disappeared or appeared broken, and styles like text colors were affected. The issues were resolved upon deactivating WPML. Solution: We initially suggested a WPML reset and reinstallation, which did not resolve the issue. After further investigation, we identified the problem was related to the PHP settings on the hosting environment, specifically the
pcre.backtrack_limit
configuration. We applied a workaround by adding the following code to the
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, 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. If necessary, please open a new support ticket in the WPML support forum.
Problem: The client is experiencing a 404 error when trying to use the Advanced Translation Editor with BeTheme, even though the documentation states that the theme is fully compatible with WPML. Solution: We recommend the following steps to resolve the issue: 1. Verify that the Site URL and WordPress URL in "Settings > General" match the actual domain you see in the browser's URL bar. If these fields are not editable, update the URL from the database or by following this article. 2. Ensure that the REST API is enabled on your site, as it is necessary for WPML's API to function correctly. If your site is in Maintenance mode, please disable it before proceeding. 3. If the 404 error persists, contact your hosting provider to check if the REST API access to your site is blocked. If so, request them to unblock it and then clear the caches from your site and browser before trying again.
If these steps do not resolve the issue or if the solution 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. Should you need further assistance, please do not hesitate to open a new support ticket in our support forum.
Problem: The client was experiencing an issue where the "Image Slider Block" plugin stopped working on the English section of their hotel categories (Europe, Asia, Middle East). The images were not displayed as a slider but just in a row underneath each other. The problem was only present in the English version, while the German version worked fine.
Solution: First, we identified that the issue was related to the HTML structure of the block, where the data settings value was being HTML encoded and then decoded incorrectly after translation with WPML's translation editor. We initially suggested translating the page using the WordPress editor and adding the slider manually on the translation page, following the documentation at https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/.
Later, we resolved the issue on the Europe hotel page by removing the problematic block and adding the following custom XML code to WPML > Settings > Custom XML Configuration tab, to exclude the "Image Slider Block" content from translation:
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, 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 with us.
Problem: The client reported that each time they duplicated a single product to another language for manual translation, all product reviews were deleted.
Solution: We recommended two workarounds: 1. Navigate to WooCommerce > WooCommerce Multilingual & Multicurrency > Settings and disable the option "By default, show reviews in all languages". 2. Alternatively, edit the file
We emphasized the importance of backing up the database and website before making any changes.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.
Problem: The client was experiencing an issue where the URLs in the Nectar Slider were not being translated correctly and were always pointing back to the English version.
Solution: We provided a workaround to address the issue with the Nectar Slider post type. Before proceeding, we emphasized the importance of backing up the database and website.
3. Apply the same workaround for button 2 URL around line 845 with similar custom code. 4. After creating and translating a Nectar Slider post, edit a page, add the Nectar Slider element, select the slider location, save, and translate the page. The internal URL will then be adjusted in the frontend.
Please note that this solution might be outdated or not applicable to your case. If it doesn't 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 open a new support ticket.
Problem:
Client was unable to find the "Last update" string in the string translation to translate it to Vietnamese. This string is from "dynamic text" from the generateblocks plugin.
Solution:
We provided an XML code to include the texts for translation. We instructed the client to navigate to WPML -> Settings -> Custom XML Configuration and add the following code:
After adding the code, the client should make a minor modification to the element containing the 'Last Update:' text, save it, and update its translation. The texts will then be available for translation and should be visible on the front end.
If you're experiencing this issue, we recommend you try the provided solution. However, this solution might be irrelevant if it's outdated or not applicable to your case. 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 the problem persists, please open a new support ticket with us.
Problem: The client is translating their site into Norwegian using WPML and wishes to make Norwegian the default language. They are seeking best practices for adding or changing content using Divi / Visual Builder, and whether they should always add content in English first. Additionally, they encountered issues with links directing to the wrong language pages and needed guidance on how to proceed.
Solution: 1. It is acceptable to set Norwegian as the main language at the end of the translation process. However, it is generally recommended to set the final default language from the beginning. Before changing the default language, always ensure to back up the website fully. 2. When making changes to the website, it is best to use the same editor that was used initially. If manual translation was used with Divi Builder, continue using Divi Builder for both languages. If automatic translation with the Automatic Translation Editor (ATE) was used, continue using ATE for translations and Divi Builder only for the main/default language. More information on the manual translation method can be found in our documentation: Using Different Translation Editors for Different Pages. 3. For the specific issues with links directing to the wrong language pages, we ask the client to open a new support ticket for each issue to allow our team to focus and investigate each problem individually.
Please note that the solution provided might be outdated or not applicable to your case. If the solution does not resolve your issue, 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. If you still need assistance, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client is experiencing an issue with a grid built using WP Grid Builder and ACF on their website. A taxonomy term labeled 'optional', which is a Translation Priority taxonomy term, is showing up under the title of each accommodation post type. Solution: We recommend customizing the Gridbuilder query to exclude the 'optional' taxonomy term from displaying on the frontend. This involves adjusting the query to only include the selected taxonomy terms that the client wishes to show.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to the client's specific case. We highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the issue persists, the client should not hesitate to open a new support ticket for personalized assistance. Here is the link to the 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
