Problem: The client is developing a site using WPML for multilingual management and is facing an issue where the header is not displaying on the product page in a secondary language. This issue occurs when the String Translation plugin is active. Solution: The issue was identified in the Woodmart theme's header settings. The 'single_product_header' string in the WPML > String Translation was incorrectly translated from 'none' to 'без' in Bulgarian. This caused the system to attempt to load a non-existent template, resulting in the header not displaying. To resolve this, the client should set the translation of this string back to 'none'.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing a critical error message when trying to translate a page using WPML, and you have debug settings enabled in your WordPress configuration, the issue might not be directly related to WPML. Solution: First, check the
debug.log
file in your wp-content folder for any fatal error messages. This will help identify if the issue is with WPML or another plugin. In this case, the error was traced back to the WooCommerce plugin, specifically an unknown format specifier in a PHP file. Since the problem originates from WooCommerce, we recommend contacting WooCommerce support to resolve this issue.
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 with us.
Problem: The client is unable to find category descriptions in the String Translation section of WPML for translation purposes. Solution: If you're experiencing issues with translating category descriptions because they do not appear in the String Translation section, we recommend using the Taxonomy Translation. Here's how you can do it: 1. Navigate to WPML → Taxonomy Translation. 2. Select the taxonomy you need to translate, such as Categories. 3. Locate the category and add your translations directly within this interface. This method is specifically designed for translating items like category names and descriptions, providing a clearer and more direct way to manage these translations compared to the String Translation section. If the category descriptions still do not appear or if there are any discrepancies, please do not hesitate to contact us for further assistance. We also suggest checking out a related discussion on this topic at https://wpml.org/forums/topic/where-to-translate-category-description-text/.
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.
Problem: The client was unable to load the Translation Management page on their site after clicking on it. Solution: Reinstall the WPML plugin.
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.
Problem: You are experiencing an error after activating the WPML String Translation plugin, even though you have enabled debugging with the following code:
. Solution: We recommend checking the contents of the
debug.log
file located in the
wp-content
directory when the error occurs. This log may provide valuable details to help identify the issue. Please share the content of the
debug.log
file with us for further assistance.
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 at WPML support forum for further assistance.
