Problem: The client was unable to translate a specific user meta field named 'dealer_overview' (Address) despite following the necessary steps for registration and adding a Custom XML Configuration. Additionally, the client faced issues translating the '/mo' text in a widget on their site. Solution: For the 'dealer_overview' field, we identified that the site was using almost 200MB of memory with a limit set to 256M in WordPress. We recommended increasing the WP MEMORY LIMIT to 384M and re-saving the user profile, which successfully registered the string for translation. For the '/mo' text issue, it was necessary to search for the string using the HTML entity in WPML > String Translation. The string was part of the 'Car Dealer - Financing Calculator' widget, and it was dynamically added, thus requiring proper coding in the widget to be translatable.
If this solution does not resolve your issue, or if it seems 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 at WPML support forum.
Problem: You are working on a multilingual website using WPML and the GiveWP plugin and are unable to find and translate the Payment Gateway Labels (e.g., "Credit Card", "Idram", "ArCa") in WPML's String Translation or in the 'Translate texts in admin screens' section. Solution: We replicated your site locally and noticed that the payment methods were not displaying due to custom label values being filled. Here's how we resolved it: 1. We removed the custom label values. 2. We deleted the associated translations. 3. We reopened the form, which then correctly registered the strings for translation again. 4. We translated the strings, such as "Credit Card", and then everything functioned correctly. This suggests there might be a plugin compatibility issue when translating custom labels, so this method serves as a safe workaround.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 further assistance is needed, please open a new support ticket.
Problem: You are unable to translate terms used inside custom product templates created in a multilingual website. The terms do not appear in String Translation or under 'Translate texts in admin screens', and translating the template ID directly was also unsuccessful. Solution: We recommend the following steps to resolve this issue: 1. Add the following XML configuration in WPML >> Settings > Custom XML Configuration:
2. Make a small change in the default language template, then open the translated template in WPML Translation Editor to apply translations. 3. Go to WPML >> String Translation, search for the default language template ID (e.g., "16122") and add the translated template ID (e.g., "16138") as a translation.
Please check if the translations appear correctly on the front end after following these steps. 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.
Problem: The client is managing a multilingual news website and encountered issues where the translation '+' button was disabled for authors and editors, displaying a message indicating lack of rights to translate from Turkish to Armenian. Additionally, the client was unable to add an author to the Translation Managers. Solution: We recommended the following steps to resolve the issue: 1. Disable all plugins except for those related to WPML from the WordPress Dashboard > Plugins, to check if the issue is caused by a plugin conflict. Reactivate them one by one to identify the problematic plugin. 2. Temporarily switch to a default WordPress theme, such as 'TwentySeventeen', via WordPress Dashboard > Appearance > Themes, to rule out theme-related issues. 3. Ensure that authors and editors are correctly assigned to translate specific pages or posts: - Navigate to WPML → Translation Dashboard. - Select the page or post and assign it to an author. - Have the author log in and go to WPML → Translations to translate the assigned content.
If these steps do not resolve the issue, we may need to request temporary access to your site to investigate further. Please ensure to back up your site before making changes, using tools like UpdraftPlus.
If this solution does not apply to your case, or if it seems outdated, please check the 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 for further assistance at WPML support forum.
Problem: The client is trying to make their website multilingual with Armenian as the default language and English and Russian as additional languages. They used the WPML Translation Dashboard to translate the website. However, in the editor, the translated version is displayed correctly, but on the live page, it still shows the Armenian text instead of the translated text. Solution: First, ensure that the server meets the minimum requirements for running WPML, which can be found here: https://wpml.org/en/home/minimum-requirements/ Next, increase the WordPress memory limit to at least 256 MB by adding the following code to the
wp-config.php
file:
define ('WP_MEMORY_LIMIT', '128M');
Place this code just before the comment:
// That's all, stop editing! Happy blogging.
If your hosting provider restricts these settings, contact them to make the necessary changes. After adjusting the memory limits, follow these steps: 1. Edit the page in the default language and make a small edit then update. 2. Open the translation and re-save it. 3. Clear the cache. 4. Go to WPML->Support->Troubleshooting and clear WPML Cache. If the issue persists after these steps, 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 still exists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to register their site with a new WPML key after the account was transferred and the previous key was unregistered. The system did not accept the new key and displayed errors indicating a mismatch and an expired account. Solution: 1. We recommended increasing the WordPress memory limit to at least 128MB by adding the following code to the wp-config.php file:
This code should be placed above the line /* That's all, stop editing! Happy blogging. */. 2. After adjusting the memory limit, the client was instructed to: - Visit https://wpml.org/account/sites/ and delete the site. - Navigate to the site's dashboard under Plugins -> Add new -> Commercial tab, unregister the site if it was still registered, and then register the site with a new key generated from the same page.
If these steps do not resolve the issue or if the solution 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 at WPML support forum.
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.
