Problem: The client was trying to translate the phone number in the header content from Catalan to Spanish and English using the Avada theme options, but the translations were not displaying correctly. The string was translated in WPML String Translation, but the issue persisted with incorrect translations showing or the fields being empty.
Solution: 1. Navigate to Avada-> Options-> Header. 2. Switch the language using the top admin bar. 3. Enter the translated phone string for the respective language. 4. Save the settings.
Additionally, the English string was incorrectly flagged as Catalan in the String Translation. We corrected the source language, which resolved the issue.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, 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 you still need assistance, please open a new support ticket.
Problem:
The frontend shows 3 instances of each category term instead of only one.
Solution:
The taxonomy was set to not translatable somehow, we have set it to translatable from WPML >> Settings > Taxonomy translation and re-saved the one of the category term and the issue is gone.
Problem: The client was trying to access the invoice for March and expected to see a charge of at least 1.99 euro, but the WPML invoice displayed a total of 0. Solution: We provided the client with a link to the invoice on Google Drive.
If this solution does not apply to your case, or if it seems outdated, we encourage you to check the related known issues, verify the version of the permanent fix, and confirm 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. For additional support, you can visit our support forum.
Problem: The client was unable to register their site with WPML due to an error stating 'Unable to parse data from service response.' Despite checking firewall rules and confirming they were correct, the issue persisted. Solution: 1. We provided a custom Google search URL to help the client find existing solutions on our support forum. 2. We requested temporary access to the client's site to investigate the issue further. 3. After confirming the WPML key and the domain URL used for generating the key, we contacted our Systems team. 4. The Systems team identified that a firewall had been triggered, blocking the request. They unblocked the request from our side. 5. We asked the client to try registering again, which resolved the issue.
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 was experiencing PHP warnings about attempting to read property "post_date" and "post_date_gmt" on null in the WPML plugin files when making changes in the backend.
Solution: We recommended the following troubleshooting steps: 1. Back up the site's database. 2. Navigate to WPML -> Support -> Troubleshooting. 3. Press the following buttons one at a time, allowing each process to complete before proceeding: - 'Disable cache for language switcher templates' - 'Clear language information and repopulate languages' (if available) - 'Synchronize posts taxonomies' for 'Products' - 'Clear the cache in WPML' - 'Remove ghost entries from the translation tables' - 'Fix element_type collation' - 'Fix WPML tables collation' - 'Synchronize local job ids with ATE jobs' - 'Synchronize translators and translation managers with ATE' - 'Assign translation status to duplicated content' - 'Set language information' - 'Reset languages' (only if no custom language was added) - 'Fix terms count' - 'Fix post type assignment for translations' - 'Cleanup and optimize string tables' - 'Clear invalid strings'
It seems that the 'Synchronize local job ids with ATE jobs' step resolved the issue for the client.
Please note that this solution might be irrelevant due to being 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, 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 our support forum.
Problem: The client was experiencing an issue where the French language version of a specific page was not showing up, and the language switcher did not display the French option. The client suspected that the problem might have been caused by a change in the URL of that page.
Solution: The client resolved the issue by duplicating the English page into French and then manually translating it. This approach was taken because it seemed that the French version of the page had been deleted. After duplicating and manually translating the page, the French language linked correctly, and the language switcher showed the French option as expected.
If you're experiencing a similar issue, we recommend trying the following steps: 1. Duplicate the page in the original language. 2. Manually translate the duplicated page into the desired language. 3. Check if the language switcher correctly displays the new language option.
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 with us.
Problem: The client was unable to see images in the translated version of their website that were visible in the native Spanish language. Solution: We recommended the following steps to resolve the issue: 1. Edit the product in the default language. 2. Activate the classic product view by navigating to the product edit page in the default language. For example: https://lovinfud.com/wp-admin/post.php?post=101&action=edit&lang=es 3. Update the product. After completing these steps, the gallery images should be copied to the translated version.
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 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 you still need assistance, please don't hesitate to open a new support ticket in the WPML support forum.
Problem: The client is managing a WordPress site and wants to use different page templates for the English and Chinese versions, based on the Japanese site. However, the changes to the page template in the target language are not being saved. Solution: We recommend two approaches to use different page templates for each language: 1. Create a separate template for each language. 2. Use the GetText call to translate the template strings via WPML-> String Translation. For detailed guidance, please refer to the following documentation:
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, 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. For further assistance, please visit our support forum.
Problem: The client reported an issue where the block titles in the Gutenberg editor were displaying in Swedish when adding new blocks to a Swedish page, despite the admin language being set to English.
Solution: Our supporter clarified that when using the WPML translation editor to translate a page and temporarily switching to the second language (Swedish) to edit the page manually, it is expected behavior for the field label in the newly added block to display in Swedish. To display the translation field label in English, the client should enable the option 'Set admin language as editing language' under User > Profile. However, this change would be lost if the WPML translation editor is used to update the translation page again. The correct workflow should be to edit the page in the original language (English), save the changes, and then update the translation in the WPML translation editor.
Lastly, we informed the client that it is not possible for the translation field label in the new block to display in English if the page language is Swedish. If the client wants the block info to display in English, they should go to ACF, edit the block, change all field labels and other info to English, and not translate them in WPML > String Translation.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, 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 with us.
Problem: The client wanted to edit the HTML markup of a Contact Form that had been translated into four additional languages but was unable to access the translations.
Solution: We informed the client that it is not possible to directly edit the translations of Gravity Forms. Instead, the client needs to update the form in the main language and then resend the form for translation. We provided a link to the documentation that explains the process: Gravity Forms Multilingual.
For the issue regarding some form dropdowns not being translated, we created a separate ticket to address that specific problem, as per our support policy of handling one issue per ticket. The new ticket can be found here: Gravity Forms dropdown translation issue.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we recommend opening a new support ticket. We also 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 need further assistance, please visit our support forum.
Problem: The client is concerned about the security of the "Advanced Custom Fields Multilingual" plugin since it has not been updated for a year and is inquiring about future updates. Solution: We assure the client that the "Advanced Custom Fields Multilingual" plugin is safe to use. We are currently working on updates, including several fixes and new features. A stable version will be released after thorough testing. In the meantime, the client can continue using the latest version of ACFML, which is 2.0.5. If the client needs further assistance, we invite them to contact us.
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 in the WPML support forum.
Problem: The client was experiencing two issues on their WooCommerce website using the Avada theme: 1. The breadcrumbs were showing "Home" instead of "Accueil" on the French side of the website in some categories. 2. The quickview panel was displaying in English (Quick view / Add to cart) instead of French (Ajouter au panier / Aperçu) in some product categories, even when on the French side.
Solution: We recommended the following steps to address the untranslated strings: 1. Navigate to WPML-> Theme and plugins localization, select the theme/plugin, and scan for strings. 2. Go to WPML-> String Translation. 3. Click on the "Translate texts in admin screens »" link. 4. Search for the required strings. 5. Select the strings and click on the "Add to String Translation" button. 6. Return to String Translation and translate the strings. 7. Clear the cache and check the front end.
Additionally, we checked the staging site and found that the issue was not present there. We advised the client to clear their live site's cache and server cache if applicable.
Please note that the solution provided 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 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 for further assistance at the WPML support forum.
Problem: The client needed to translate text in the footer that was built using SiteOrigin's layout builder and appeared in English. Solution: We recommended the client to navigate to WPML > String Translation and search for the string they want to translate. For further guidance, we provided a link to our documentation on how to find strings that do not appear on the String Translation page:
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, 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 visit our support forum at WPML support forum.
Problem: The client needed to translate the parent menu item text on the main menu. Solution: We recommended following our documentation to translate the menu into the Thai language. Here are the steps: 1. Visit the WPML documentation on translating menus: Translating Menus. 2. Follow the instructions provided in the documentation to create and translate the menus manually.
If this solution does not apply to your situation because it might be outdated or not relevant to your case, we suggest opening a new support ticket. We also 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 further assistance is needed, please contact us in the WPML support forum.
Problem: If you're using "automatic translation" to translate your site from English to Thai and you notice that the layouts on Thai pages are incorrect, with sections or partial content appearing twice, we can help. Solution: First, ensure you have a full backup of your site. Then, follow these steps: 1. Apply the workaround provided in our documentation: Page Builder by SiteOrigin - Layout Builder Widgets Not Translatable When Duplicated Inside and Outside Layout. 2. Edit the page in English and make a small change to the content. 3. Save the changes and update the translation page to fix the issue. For widgets from third-party plugins, such as the Table of Content widget, you will need to edit the translation page in the Thai language and re-add the widget before saving.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking for 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 don't hesitate to open a new support ticket with us. Contact WPML support.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
