Problem: The client is experiencing an issue where the product pagination shows 25 products on the first page, but the number decreases on the second page in both Italian and English versions. This issue is suspected to be caused by a conflict between WPML and the Woo Products component due to the use of identical category names and slugs in different languages.
Solution: We recommend the following steps to resolve the issue: 1. Ensure that product categories are correctly translated to avoid confusion. 2. Remove duplicate name categories or ensure that products are assigned to the correct categories. 3. Adjust the query of the element to use "All products" instead of matching by category to see if the issue persists.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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 reported that the image under the header was not displaying on their multilingual site when using Elementor and WPML. Solution: We recommended translating the template where the image was added and then using the translated template's shortcode in the translated block under the header template. This approach ensures that the banner displays correctly in the different language versions of the site.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is relaunching their site to be multilingual and wants to know if they can set the greenbox.dk domain as the Danish domain and start translations even though it is not yet a parked domain. They are also concerned about whether they need to stop web hosting and park the domain before starting translations. Solution: We recommend adding your domain even now by unchecking the validate option and saving. It's crucial to ensure that the domains are set up correctly before proceeding with translations. Domains should work and open the same website content without redirecting. If the domain isn't working correctly yet, we advise against using that mode until the domains are ready. You will not be able to check translations on the frontend in this case. Meanwhile, you can use another language mode, like language per directory, and translate your website. Once the domains are ready, you can switch to the domain per language mode.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket or visiting the WPML support forum.
Problem: The client is experiencing issues with the WPML plugin not fetching all accommodation English version data for translation into Spanish. Additionally, there is a recurring problem with the contact form, which stops working after previously being resolved by disabling the cache option. Solution: 1) We resolved the contact form issue by translating the global section from which the form originates. We recommend checking if the form now functions correctly on the translated accommodation page. 2) For the calendar issue, we translated the rate for the accommodation type, which was not previously translated. Please verify if the calendar now displays correctly in both languages. 3) For untranslated strings below the calendar, we suggest translating the body templates to resolve this issue.
If these solutions do not resolve your issues or if they seem outdated, we highly recommend opening a new support ticket. Also, 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. For further assistance, you can contact us through the WPML support forum.
Problem: You are experiencing a styling issue in the backend when using the Gravity Forms Multilingual addon, resulting in a broken UI. Solution: We recommend disabling the No Conflict mode in your Gravity Forms settings. This mode, when enabled, prevents third-party scripts from affecting the Gravity Forms administration pages, which can lead to styling conflicts. To disable it, edit your form settings and turn off the No Conflict mode. For more detailed instructions, visit the Gravity Forms documentation: https://docs.gravityforms.com/enabling-no-conflict-mode/
If this solution does not resolve your issue or seems outdated, 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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client was facing issues with WPForms not translating 'United States' to Arabic and the navigation menu changing unexpectedly after attempting to translate the currency switcher. Solution: We logged into the client's site and successfully translated 'USD' to Arabic, ensuring it displayed correctly on the frontend without affecting the navigation menu. We recommend clearing your cache if you encounter similar issues, as this might resolve temporary display problems. Additionally, we registered the currency label for translation via the Admin screen. You can now navigate to WPML > String Translation, search for the currency, and translate it into other languages.
If this solution does not apply to your case, or if it seems outdated, 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. If issues persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: You are trying to update the German text via the WPML tool after updating the English text, but the German text reverts to the updated English text after clicking 'translation complete'. Solution: We recommend following these steps to ensure the German text updates correctly: 1) Open the page in the original language. 2) Add an extra letter to the page's title, update it, then remove the changes and update the page again. 3) This action should trigger the page translation and show that it needs to be completed. 4) Open the translation editor, confirm the translation for some fields, and complete the translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to 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 the problem persists. You can do so at WPML support forum.
Problem: The client is experiencing a loop issue when users attempt to reset their passwords using the 'WooCommerce Multilingual & Multicurrency' plugin. Instead of being redirected to the password reset form, users are redirected back to the initial form requesting their email or username. Solution: We identified that the issue might be related to the WooCommerce Endpoints (Store URLs) settings in the WooCommerce > WooCommerce Multilingual & Multicurrency > Store URLs section. We recommend checking these settings and ensuring they are correctly configured. Additionally, performing a full backup before making any changes is advisable.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Also, please check the related known issues and verify that you have installed the latest versions of themes and plugins. For further assistance, you can contact us through the WPML support forum.
Problem: The client is using a plugin for custom tabs in WooCommerce product pages, but the text in these custom tabs is not appearing for translation in WPML. The client has tried making the tabs translatable in WPML settings and searching for them in string translation without success. Solution: First, ensure that the plugin used is compatible with WPML. For instance, WPML supports the 'Custom Product Tabs for WooCommerce' by Yikes, which can be checked here: https://wpml.org/plugin/custom-product-tabs-for-woocommerce/. If the plugin is compatible, follow these steps: 1. Make the tabs translatable in WPML settings. 2. Go to your product, make a small change, and update it. 3. Access the translation editor to see if the tabs are now listed. If the tabs still do not appear, you might need to add a language configuration file as per the WPML documentation here: https://wpml.org/documentation/support/language-configuration-files/. Alternatively, you can manually translate the tabs: 1. Go to your product in the default language. 2. Use the language switcher in the backend and switch to the translation. 3. Locate the tabs, add the translation, and update.
If these solutions do not resolve the issue or if they seem outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client noticed that the category name on their product page was in Arabic, and the link was pointing to an Arabic version, suggesting a potential issue with WPML. Solution: We first noted that the client's website was experiencing a database connection issue. After resolving that, we recommended changing the Taxonomies Translation settings by navigating to Taxonomies Translation settings. Following this adjustment, we advised the client to clear their browser cache to ensure the changes take effect.
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 was unable to translate a widget on their multilingual site. Despite adding the widget multiple times and translating it via WPML's String Translation, the widget content was only displaying in Greek, regardless of the language selected. Solution: We took several steps to resolve the issue: 1. We ensured that the 'text_admin' string was registered in WPML's String Translation. 2. We resaved the German translation by adding a space and then removing it. 3. We resaved the page translation, even though the content was not directly from the page itself. 4. Finally, we purged the cache to ensure that the changes took effect.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: If you're experiencing an issue where the footer on the contact page is not translated, despite being translated on other pages of your website, it might be due to a caching issue. Solution: We recommend clearing your cache thoroughly after updating the widget for the specific language. Additionally, ensure that you have saved the 'admin texts' in the 'String Translation' and then saved the page again. To automate the registration of these texts, you can add the following code in 'WPML > Settings > Custom XML Configuration':
This solution might be 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 this does not resolve your issue, please open a new support ticket.
Problem: If you're noticing that some translated pages are appearing on Google even though they haven't been published, and these pages display incorrect logos and theme colors, this might be due to a settings conflict or a compatibility issue. For instance, if your site's translated product page shows a different logo or theme colors compared to the original English page. Solution: First, ensure that you have not inadvertently published the product translations. Check your Translation Preference settings for the Product Post Type and Product Categories Taxonomy. You should have the 'Translatable - use translation if available or fallback to default language' option selected. This setting allows the default language products to be listed in the secondary language on the frontend without translation or content duplication. Next, verify that your Elementor templates for the Header, Footer, and Single Product are translated into the secondary language. You can do this by accessing the following links in your admin area:
If after these checks the issue persists, it might be 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 you need further assistance, please do not hesitate to open a new support ticket or visit our support forum at WPML Support Forum.
Problem: The client is facing issues with reactivating WPML on their website after a rebuild. The main problems include a database error stating 'We have detected a problem with some tables in the database,' no languages appearing in WPML -> Languages, and inability to add languages manually. Solution: We recommend resetting WPML and then reinstalling it. Here are the steps to follow: 1. Go to WPML -> Support -> Troubleshooting. 2. Scroll down to find the 'WPML Reset' option and use it to reset WPML. 3. Reinstall WPML with a fresh download. These steps were tested on a staging site and resolved the issues. If you're experiencing this, we recommend trying these steps on your live site.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 with us for further assistance.
Problem: You are experiencing an issue where the links within your custom dropdown menu (megamenu) created using a UX Block and translated with WPML still direct to the original language pages instead of the translated pages. Solution: First, ensure that the 'terms' shortcode parameter used in your menu is translated. Follow the detailed instructions on how to translate custom shortcodes with WPML here: https://wpml.org/documentation/support/language-configuration-files/translate-custom-shortcodes-with-wpml/. Next, add the following custom PHP code to your theme's functions.php file to make the 'terms' ID translatable:
This will allow you to translate the text and ID for your menu in the translated languages.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
