Problem: The client created pricing forms using the WooCommerce plugin and AcoWebs WooCommerce Custom Product Addons plugin. The forms function correctly in the first language, but issues arise with displaying or hiding fields using the Global Attribute in other languages. Solution: We noticed that the missing fields do not have the same settings among languages in the conditional tab. We recommend checking the settings in each language to ensure consistency. Unfortunately, the plugin documentation does not mention the recommended method for translating the conditional tab, and the field in the translated add-on is greyed out, making it unchangeable. We advise contacting the plugin's support team to inquire about the custom field name, which will allow you to set it to either copy once or translate and change it to the translated version. For further guidance, you can refer to the plugin documentation here: Acowebs Plugin Documentation.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket at WPML Support Forum.
Problem: The client is experiencing issues with WooCommerce categories not displaying correctly in both the primary and secondary languages on their shop pages. The problem began after adding a new category called 'Our Services'. Specifically, some child categories are not visible or display incorrect counts, and links lead to 'Page Not Found'. The issue resolves when all WPML plugins are disabled. Solution: We recommend disabling or clearing the Object cache as it can sometimes cause issues with WPML. This action often resolves discrepancies with category displays and translations. For further guidance on managing Object cache issues with WPML, please visit the following link: WPML and Object Cache Issues
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 problems persist, please open a new support ticket at WPML Support Forum for further assistance.
Problem: You are trying to configure language-specific sitemaps using All-in-One SEO for your site, but the current sitemap includes links to pages for both English and French languages, and you want to create separate sitemaps for each language. Solution: Currently, it is not possible to separate the generated sitemap file as this is how the All-in-One SEO plugin operates. We recommend using WPML's hreflang tags to inform search engines about the default language of the page’s content and the translations available in different languages.
If this solution does not apply to your case because it might be outdated or not suitable for your specific situation, 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.
Problem: The client is unable to access WPML>>Settings>>Taxonomies Translation due to a fatal error indicating a type mismatch in WPML_WP_Roles::get_highest_level(). Solution: We recommend logging in as a different admin user to verify if the issue persists. Additionally, it's crucial to perform a full site backup before attempting any fixes. You may also want to try the workaround suggested in a related support ticket, which can be found here: related support ticket.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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.
Problem: The client is unable to see the translated product brands in French on their website using the Kadence Theme Shop Kit. The brands are visible in English but not French and the language selector is missing when editing a brand. Solution: We recommend checking if the Product Brands taxonomy is set as Translatable in WPML. You can do this by navigating to WPML>>Settings>>Taxonomies Translation.
If the issue persists, please perform the following troubleshooting steps after ensuring you have a full site backup:
1) Visit WPML>>Support page and click on the Troubleshooting link. 2) On the Troubleshooting page, click on the following options in the *Clean up* section and wait for confirmation after each: - Clear the cache in WPML - Remove ghost entries from the translation tables - Fix element_type collation - Set language information - Fix WPML tables collation - Assign translation status to duplicated content - Fix terms count - Fix post type assignment - Cleanup and optimize string tables
If these steps do not resolve the issue, the 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.
Problem: The client was experiencing an HTTP ERROR 500 when trying to switch to the French language in the Admin dashboard. Solution: We identified that the issue was related to a known problem with the Kadence Blocks and Kadence Blocks Pro plugins. We provided a workaround that involves the following steps: 1. Temporarily deactivate the Kadence Blocks and Kadence Blocks Pro plugins. 2. Activate WPML String Translation. 3. Delete the problematic strings as described in the errata page: https://wpml.org/errata/kadence-pro-plugin-sprintf-too-few-arguments/. After applying this workaround on a staging site, the issue was resolved, and we advised the client to test it on their staging site before applying it to the live site.
Please note that this solution might be 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 open a new support ticket in the WPML support forum.
Problem: The client is unable to find the string to translate hover text "from 72 units" in the WPClever Badge Management plugin. Solution: We recommend checking if the string has been recognized but not yet associated with the String Translation panel. To do this, navigate to WPML>>String Translation and click on the Translate texts in admin screens » link at the bottom of the page. Search for the missing strings on the Admin Texts Translation screen. If found, add it for translation and then translate it. For more detailed instructions, please refer to our documentation: Finding strings that don’t appear on the String Translation page.
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 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 do not hesitate to open a new support ticket. You can reach our support forum here: WPML support forum.
Problem: The client is unable to find the string to translate the "Login / Register" button text that is being replaced using a Code Snippet.
Solution: We recommend using the
wpml_register_single_string
and
wpml_translate_single_string
hooks to register and retrieve the translation for strings stored in the database by a snippet plugin. Here is a sample code to illustrate how to use these hooks:
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the solution does 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 you still need assistance, please open a new support ticket. You can do so by visiting our support forum.
