Problem: The client is experiencing issues with the template layout for their theme after adding several languages using WPML. Specifically, the Home and Contact Us pages are not being picked up properly by WPML, resulting in different layouts for these pages after translation. Solution: We recommend checking if the page options are fully copied over for the affected languages. In this case, the French language pages were not displaying correctly because the page options were not fully copied. To resolve this, you can follow the steps provided in this video tutorial: https://go.screenpal.com/watch/cZXUD7nVRYU.
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 issues persist, please open a new support ticket at our support forum.
Problem: You are trying to translate the Kadence Advanced Form (Adv) block using WPML, but the translations are not visible in the Advanced Translation Management (ATM) or among the strings. Solution: First, ensure that the issue is due to the compatibility of the Kadence Blocks with WPML by checking our errata page at https://wpml.org/errata/kadence-blocks-new-blocks-are-not-compatible-yet/. If the issue matches, follow these steps: 1. Navigate to WPML > Settings > Custom XML Configuration. 2. Add the following XML configuration:
3. Click the Save button. 4. Edit the form and click the Update button. 5. Translate the form again. This should resolve the issue, allowing you to see and manage the translations in WPML.
If this solution does not apply to your case, or if it 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was experiencing a blank white page when trying to use the Advanced Translation Editor (ATE) on their website. Additionally, after attempting a solution, they encountered a 'Critical Error' message. Solution: 1. We suggested making a minor edit to the primary language page to refresh the ATE and then retranslate the page. 2. When a 'Critical Error' occurred, we advised the client to perform a full backup of their website/server. 3. We identified that the server lacked the 'Multibyte String Extension', which was necessary for the ATE to function properly. We recommended checking if this extension was available and activating it on their hosting.
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 problems persist, please open a new support ticket.
Problem: The client is trying to display languages in the footer menu of their website, similar to another website. They are experiencing an issue where they need to click 2-3 times on the language switcher before being redirected to the selected language, and sometimes it doesn't work at all. Solution: We noticed a delay in the page loading after clicking the language switcher, which might cause the impression that the link isn't responsive immediately. This could be due to the session data being transferred between domains when switching languages. We recommend the following steps to address this issue: 1. Navigate to WPML > Languages. 2. In the Language URL format section, find the option to pass session data through a language switcher and select "Disable this feature". 3. Save the changes. 4. Resave the permalink structure by going to Settings > Permalinks. 5. Clear the caches from your site and browser. After performing these steps, check if the issue persists.
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 is unable to load jobs in the WPML translation queue on their website.
Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Create a new user with an Admin role. 2. Log in through this user in a new browser or incognito window. 3. Check if you can now see the translations.
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: You've updated icons on your homepage using Elementor, and initially, everything appeared fine. However, the content and icons reverted back over the weekend. You're experiencing issues where the homepage content changes automatically. Solution: If you're experiencing this issue, it's important to use a consistent method for making changes to your content. Mixing translation methods, such as manually updating content in one language and using the WPML editor for another, can lead to content loss. Each time you save the page in the default language, it will overwrite any manual changes made in a second language. We recommend choosing one method and sticking to it. For detailed guidance on using different translation editors, please visit: Using Different Translation Editors for Different Pages.
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 for further assistance.
Problem: The client is facing an issue where the canonical URL for duplicate posts is incorrectly pointing to the original English UK version instead of the intended version.
Solution:
When you duplicate a post, the canonical will point to the default language. That's expected behavior (to avoid duplicate content).
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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported an issue with the HTML sitemap on their website using WPML and Rank Math SEO. The sitemap displayed Ukrainian titles for pages but linked to the Czech versions, and it did not include other language versions correctly. Additionally, all pages for the Ukrainian language were marked with a noindex tag, making them invisible to search engines. Solution: We recommended the client to follow these steps: 1. Install the WPML SEO add-on from Plugins -> Add new -> Commercial tab. 2. Re-save the permalinks. 3. Apply the workaround described in the errata page: https://wpml.org/errata/rankmath-rank_math_html_sitemap-shortcode-lists-html-sitemap-in-all-languages/. 4. Check if the issue is resolved. If these steps do not resolve the issue, we recommend creating a staging site and testing by deactivating all plugins and reactivating them one by one to identify the culprit. Start with a default WordPress theme and only WPML plugins and RankMath SEO activated.
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 at WPML support forum.
The client was experiencing a critical PHP Fatal error when trying to access ACF options in the WordPress Admin Area, specifically related to the WPML plugin.
2. We conducted tests on both our testing servers and the client's staging site. The issue was not reproducible locally but occurred on the staging site only when the Speed Optimizer plugin from SiteGround was active. We advised the client to deactivate the Memcached option in the Siteground Speed Optimizer plugin, which resolved the issue.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the WPML String Translation plugin, which disrupts the CSS and affects the display of Avada options in the backend. Solution: We recommend checking if the Avada parent theme, Avada Core, and Avada Builder plugins are updated to their latest versions. If after updating, the problem still persists, it might be helpful to check for conflicts with other plugins. Updating all plugins can resolve such issues. If the issue continues, we suggest providing access to your site for further investigation. Please ensure to back up your site files and database before providing access. For more details on privacy and security, visit our privacy and security policy.
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. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: You are trying to find a specific string in String Translation that appears in the Popup of the mini-cart after adding a new product or when clicking on a cart icon. This string is not found in String Translation or WooCommerce files, and it persists even when switching to the built-in theme. Solution: We recommend trying two methods to locate and translate the missing string: Method 1: Navigate to WPML > String Translation, and at the bottom of the page, enable the checkbox labeled "Look for strings while pages are rendered." Then, visit the front end where the string is displayed, and return to WPML > String Translation to search for the string. Method 2: If the string is not found in WPML > String Translation, it might be included as an admin text string. You can find the typical process for translating these strings here: Translate Admin and Settings Strings Related documentation can be found here: Finding Strings that Don't Appear on the String Translation Page Please note, if the strings originate from outside of WordPress, WPML will not be able to detect or translate them.
If this solution does not resolve your issue or 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 problem persists, please open a new support ticket for further assistance.
Problem: The client was experiencing issues with menu synchronization and display across different languages (ENG, ESP, FRA) on their website. Despite translations being available, menus and header templates were not appearing correctly in languages other than English and Italian.
Solution: 1. We recommended updating the WPML plugin and all related add-ons to the latest version to ensure compatibility and functionality. 2. For the header not displaying in other languages, we advised translating the Header and Footer templates using the 'Header Builder' and ensuring these templates are selected in the theme customizer. 3. To address the menu display issues, we suggested adjusting the menu order in the default language and resyncing the menus using this guide: Translating Menus. 4. For the page contents not showing in other languages, we recommended making a minor edit to trigger a translation update and ensuring all sections are fully translated. 5. If issues persist or if the solution provided here does not apply due to updates or differences in 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 further assistance is needed.
Problem: The client was experiencing an issue where after renaming attributes and changing their slugs in YITH ajax product filters, the new names were not appearing in the filter settings dropdown. Instead, the old names were displayed. This issue was suspected to be related to how WPML manages terms. Solution: We recommended the client to: 1. Create a full backup of the site. 2. Update all outdated plugins and themes, especially the WPML plugins. This can be done in Plugins -> Add new -> Commercial tab -> Click on the button to search for new versions -> Download and install the latest version of the WPML plugins. 3. Flush any cache memory that might exist. 4. Apply the workaround described in this errata page: https://wpml.org/errata/wordpress-6-7-mo-files-not-loaded-and-leading-to-missing-translations-on-front-end/ 5. Go to Woocommerce -> Woocommerce Multilingual & Multicurrency -> Status tab -> Fix any error that might appear in the first two sections. 6. Edit the filters manually on the secondary languages and manually add the changes to the configuration of each translated filter -> Save the changes -> Double-check if the issue disappeared.
If the solution provided here does not resolve your issue or 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 problem persists, please open a new support ticket at WPML support forum.
Problem: The client needs to automate the 'Set prices in other currencies manually' option for all new and existing products in their WooCommerce store. Manually setting this for over 5000 products is not feasible. Solution: We recommend implementing a custom code solution, as WooCommerce Multilingual does not support this functionality by default. For new products, adapt the code by changing the value for
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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client has a number of ACF fields, including a repeater field with an image subfield and a text subfield. The issue arises when trying to handle translations for these fields in a duplicated page. Solution: If you're experiencing this issue, we recommend setting the repeater field to 'COPY' if you want the changes in the default language to be copied or synced to the second language. This setting is necessary when the page is duplicated and you wish to add translations independently. For more detailed guidance on setting up your ACF fields with WPML, please visit our documentation on Recommended Custom Fields Translation Preferences for ACF and WPML.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
