Problem: In the English language, products are not showing in the category. Solution: If you're experiencing this issue, we recommend you try the following steps: - Go to your WordPress Dashboard. - Navigate to WooCommerce > WooCommerce Multilingual & Multicurrency > Multicurrency (tab). - Under the currencies, uncheck the Show only products with custom prices in secondary currencies checkbox. For more information, please visit Multi-Currency Support in WooCommerce.
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 is experiencing issues with the navigation menu on mobile devices. The menu does not open on the homepage, but it works on other pages. Solution: We recommend deactivating the WPML plugin temporarily to check if the issue persists. This step will help determine whether the problem is related to WPML or if it might be a conflict with the theme's styling.
If the problem continues after deactivating WPML, it suggests a potential conflict with the theme rather than an issue with WPML itself. In such a case, checking the theme's settings or contacting the theme's support might be necessary.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, 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 open a new support ticket at WPML support forum.
Problem: The client reported an issue where HTML paragraph breaks were not being recognized in the Translation Editor, causing all text to appear in one block without proper separation in translations. Solution: We recommended switching to the older version of the Advanced Translation Editor where this issue might not occur. Detailed instructions for this process can be found here: https://wpml.org/errata/html-attributes-not-available-for-translation-in-advanced-translation-editor/
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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is using WPML with Crocoblock on their website. The Crocoblock filter widget and Listing Item work correctly in German, the default language, but issues arise when switching to French: the filter widget appears empty, and no listings are displayed, and the content of a Listing item disappears when switching from German to French. Solution: 1. For the filter widget appearing empty and no listings displayed in French: - Edit the French home page and replace the custom query with a standard posts query to ensure items appear correctly. - Ensure that two fields in the filter have the same values in both languages. Set the correct values in French and verify by checking the strings in String Translation.
2. For the content of a Listing item disappearing when language is switched: - Navigate to WPML-> Settings-> Custom Fields Translation. - Enable the "Show 'Multilingual Content Setup' meta box on post edit screen" option and save. - Edit the post in the default language. - Scroll down to the "Multilingual Content Setup" section. - Set the custom fields to Translate, Copy, or Copy once. - Click "Save" and update the page in the default language.
If these steps do not resolve your issues or if the solution 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client's homepage has been translated from English to Italian and Spanish. While the Italian and English versions work correctly, the Spanish version displays the title in English in social shares, despite being translated and saved in Spanish. Solution: If you're experiencing this issue, we recommend installing the WPML SEO addon if you haven't already, as it is required for proper integration with Yoast SEO. After installation, make a minor edit to your default language page, save it, and then re-translate the page. For detailed guidance, please refer to our documentation on Using WordPress SEO with WPML.
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 at WPML support forum for further assistance.
Problem: You need to translate JetEngine Forms using WPML but are unsure how to proceed. Solution: First, ensure that the JetEngine Form post type is set to "Translatable". You can do this by navigating to WPML > Settings > Post Types Translation, then find the form post type and set it to Translatable. After setting the form to translatable, according to JetEngine's documentation, you should duplicate the form and edit the duplicate to add your translation. Finally, manually add the translated form to the second language. For more details, please check the JetEngine documentation on translating forms here: JetEngine Documentation on Form Translation.
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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum.
Problem: The client needed to translate archive pages for custom post types (CPTs) and deactivate/delete unwanted indexed translated archive pages. Solution: We recommended manually registering the CPTs to avoid issues with translations and indexing. Additionally, the client provided a custom code snippet to disable the archive slug for some CPTs in all languages other than the default. Here is the code snippet:
will fetch posts only in the specific language by bypassing WPML filters.
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.
Problem: The client is facing an issue where the Pagelist component within a Navigation block is not correctly pointing to the English homepage in a multilingual setup. The settings for the Pagelist component are duplicated across both Dutch and English versions when trying to translate the pattern or template part. This results in navigation issues, particularly when switching languages, leading to broken links and 'page not found' errors. Solution: We recommend performing a full backup of your site before proceeding with any changes. After backing up, you should verify the slug changes for your homepage in each language. Specifically, ensure that the slug for the Dutch homepage does not interfere with the WPML functionality. If issues persist after checking and adjusting the slugs, we suggest deactivating plugins temporarily to identify if any are causing redirection issues. If the problem remains unresolved, please consider opening a new support ticket with us for further assistance. Additionally, 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 this solution does not resolve your issue or seems irrelevant, please do not hesitate to open a new support ticket with us for personalized assistance. Visit our support forum at WPML Support Forum.
Problem: The client reported that the 'Link to translation' feature, which was previously visible in posts, suddenly disappeared despite having translations available and being updated to WordPress 6.6.1. Solution: We identified that the issue might be due to the String Translation plugin not being active. We recommend activating the String Translation plugin on your site and then reconfiguring the 'Link to Translation' feature. If you haven't installed the addon yet, please go to Plugins > Add new > Commercial and install the addon from there. Here's a guide on how you can configure that.
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.
Problem: The client was experiencing an issue where product variations were not visible or editable in the English version of their WooCommerce store, while in the Lithuanian version, variations were visible but not editable. Solution: We recommended the client to perform troubleshooting actions from WooCommerce Multilingual. Specifically: 1. Navigate to WooCommerce->WooCommerce Multilingual->Settings->Troubleshooting. 2. Execute the following actions: - Sync products variations - Fix translated variations relationships After these steps, it was necessary to regenerate the variations for the affected products by going to the product edit page and clicking on 'Generate variations'.
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: After adding custom code to functions.php to populate post grids in a second language, the 'Intro' field from Unlimited Elements Post Grid is not translating correctly and is pulling data from the original language post. Solution: We recommend the following steps to address the issue: 1. Navigate to WPML > Settings and temporarily switch to the Classical Editor. 2. Complete the translations that were problematic. 3. Return to WPML > Settings and switch back to the Advanced Translation Editor (ATE). 4. Continue and finish translating the post.
If this solution does not resolve your issue or seems outdated, we highly recommend checking for 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 the problem persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to manually translate content using the Advanced Translation Editor in WPML, despite having disabled the automatic translation option. The translation box was not appearing as expected. Solution: We first suggested that the client click on the empty space where the translation box should appear, as it might still trigger the box to show up. When this did not resolve the issue, we confirmed that the client was using a new version of the Advanced Translation Editor that had been released recently, I suggested to revert to the previous version with the desired translation box. We then directed the client to follow the instructions on https://wpml.org/errata/html-attributes-not-available-for-translation-in-advanced-translation-editor/ to see if they could revert to the older Advanced Translation Editor.
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 is unable to review translations on their site when Elementor Pro is activated, encountering a PHP fatal error due to a missing format specifier in a translated string. Solution: If you're experiencing this issue, we recommend making a full backup of your website first. Then, ensure that the dynamic part of the problematic string matches the original. For example, a correct translation in German should look like this:
Sie sind eingeloggt als %1$s (%2$sLogout%3$s)
You can locate and correct this translation in WPML > String Translation by searching for "You are logged".
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: When updating translations, all apostrophes in Divi Toggle module titles are incorrectly replaced with triple apostrophes across the entire page, not just the edited content. The existing workaround in functions.php from WPML support pages is not resolving the issue. Solution: If you're experiencing this issue, we recommend updating your functions.php file with the following code to correctly decode special characters like apostrophes and ampersands in Divi module titles:
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 at WPML support forum for further assistance.
Problem: You are trying to translate your WordPress site using WPML, specifically having issues with a page not being translated to other languages. Sometimes translations appear with a strange URL, but currently, they are not appearing at all for this specific page. Solution: We recommend checking the language switcher on the top bar of your site. From there, you can access other language versions of the page and ensure they are published. If the translations still do not appear or show with strange URLs, it might be due to settings or the need for updates.
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 at WPML support forum for further assistance.
