Problem: You are using the WPML plugin with the Flatsome theme, and after activating WPML, your website stops working, displaying either a white page or an error message stating that the site is currently unable to handle the request. Solution: The issue is due to fatal errors related to the missing 'DOMDocument' class, which indicates that the PHP-XML extension is not installed or enabled on your server. This extension is crucial for WPML as it relies on it for XML parsing. To resolve this, check if the PHP-XML extension is installed and enabled on your server. You might need to contact your hosting provider or refer to your server's documentation to ensure the extension is properly installed. For further guidance, visit WPML support forum.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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.
Problem: You are trying to set a different logo for each language on your multilingual website using WPML. Despite using WPML's 'String Translation' feature and translating the logo IDs for each language, the logo does not change when switching languages. Solution: We recommend following these steps to ensure the logo changes correctly for each language: 1. Navigate to WPML >> String Translation page. 2. Click on the “Not seeing strings that you are looking for?” section and then click the Admin texts translation link. 3. Search for the logo ID and enable its translation. 4. Return to the WPML >> String Translation page and add the translated logo ID. This should allow the correct logo to display for each language on the frontend. You can update the translation as needed from the String Translation page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket.
Problem: The client was facing an issue with the design of the language switcher on their multilingual website, specifically the Armenian version. The language switcher was missing a small arrow and a border line inside the dropdown. Additionally, the client was unable to update plugins as the update option did not appear, and the OTGS Installer could not be activated. Solution: We advised the client to check for updates in the Plugins->Add new -> Commercial tab or download the latest versions manually from https://wpml.org/account/downloads/. For the design issue of the language switcher, it was identified that the theme's CSS controls the display, and the missing div class for the submenu in the Armenian version was causing the issue. We recommended adding a translation for the Armenian version in Appearance->Menus to resolve this. After updating the WPML plugins to their latest versions, we instructed the client to go to WPML->Translation Management, filter by RU, and send the Elementor templates for translation to fix the header template issue.
Please note that this solution might be 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 needed, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client wants to change the Armenian language code in their website's URL from 'hy' to 'am'. Solution: We explained that it is not possible to change the language code of existing languages directly. However, we recommended adding a new language with the desired language code 'am'. To do this, the client should follow the steps provided in our documentation:
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are trying to set the default language of your custom taxonomy values to English in WooCommerce Multilingual, but despite following the documentation, you have been unable to achieve this. Solution: On the editing screen of your custom taxonomy, you can manually change the language of each term. For example, if the term is '1 Adult', you can set its language to English directly on the term's editing screen. If you encounter further issues or need additional assistance, please provide your site's debug information, which you can learn about here.
If this solution does not apply to your case, or if it seems outdated, 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: The client is unable to find the translation strings for the names of the months in the product description within the Cart on a website using the Easy Booking Pro plugin. Solution: If you're experiencing this issue, we recommend checking the WPML -> Strings Translation section. For guidance on how to use this feature, please read our guide on Strings Translation. If you do not find the strings there, you might need to look for strings that are not appearing on the Strings Translation page. Please consult our guide on finding other strings. Should these steps not resolve your issue, it may be helpful to share your site's Debug information with us for further assistance. You can find instructions on how to provide this information here.
Please note that the solution provided 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 trying to translate products with WooCommerce Multilingual, the following error appears:
An error of type E_ERROR was caused in line 124 of the file ......./wp-content/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-validate-html.php
Error message: Uncaught Error: Call to undefined function mb_ereg_replace_callback() in ......./wp-content/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-validate-html.php:124
Solution: The 'Multibyte String' PHP extension was not being enabled on the server. We recommend that you contact your hosting support and ask them to enable the 'Multibyte String' PHP extension. This extension is necessary for WPML to work properly. Please check the WPML’s Minimum Requirements. For more information on the 'Multibyte String' PHP extension, you can visit the PHP manual at https://www.php.net/manual/en/book.mbstring.php. If this solution doesn't look relevant, please open a new support ticket in our forum at https://wpml.org/forums/forum/english-support/.
Problem: After installing the WPML Multilingual CMS plugin, the site admin panel stops working and displays a critical error. The error message indicates that the class 'DOMDocument' is not found, which is part of a PHP extension that may not be enabled on the server. Solution: If you're experiencing a critical error after installing the WPML Multilingual CMS plugin and the error message mentions that the 'DOMDocument' class is not found, we recommend checking if the PHP XML extension is enabled on your server, as the 'DOMDocument' class is part of this extension. A similar issue was resolved by another client, and you can follow the steps provided in this thread: https://wpml.org/forums/topic/fatal-error-when-trying-to-access-installed-plugin/#post-12615561.
