Problem: The client is attempting to change the folder name for interface-wpml-log.php located in the 'logs' folder within the classes directory. This is because many servers exclude logs folders from backups, causing the file not to be restored. Solution: We advise against changing the folder name for interface-wpml-log.php due to potential conflicts or fatal errors. Changing the folder name would require updates to multiple files, specifically the following autoloader files:
. 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to merge two sites, one in English and one in Hebrew, into a single WPML-powered site, using the English site as the base. Solution: 1) Set the English version as your main default language. 2) Export the Hebrew content from the second website and import it into your main site. Unfortunately, there isn't an integrated function in WordPress/WPML for this task, so you might need to use additional plugins or tools. 3) If you wish to maintain separate domains for each language, set up a Multi-Domain configuration. You can find detailed instructions here: How to use WPML with different domains per language. If you encounter difficulties with content import, consider hiring a certified contractor. You can find our certified partners here: WPML Contractors.
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 this does not resolve your issue, please open a new support ticket.
Problem: The client reported issues with the Litho Fancy Box not functioning correctly in RTL mode, specifically in Hebrew, and the blog not displaying in German and Hebrew. Solution: 1. We suggested clearing the browser's cache to resolve any immediate discrepancies in how content is displayed. 2. We confirmed that WPML supports RTL languages and advised ensuring that the theme used is compatible with RTL and WPML for optimal performance. For more details, visit WPML RTL support documentation. 3. Upon further investigation, it was discovered that the 'Blog' page and its posts lacked Hebrew translations. We recommended completing the translations to resolve the issue.
If this solution does not resolve your issue or seems outdated, please check the related known issues and verify you have the latest versions of themes and plugins installed. If the problem persists, we encourage you to open a new support ticket.
Problem: The client is using the My Sticky Elements plugin and needs help translating it from English to Turkish. Solution: We recommend checking if the My Sticky Elements plugin is developed according to WordPress developer standards for internationalization (i18n) and uses getText() calls. If so, you can register the strings for translation as outlined in our guide on finding and translating strings that don't appear on the string translation page. You can find the guide here: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page.
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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client reported two issues: one on the shop page and a translation problem on both Translation Management and Page translation. Specifically, the 'Edit translation' option was not working and was not clickable.
Solution: For the first problem, we recommended the following steps: - Navigate to Plugins -> Add New -> Commercial in your website. - Unregister WPML by clicking the unregister link. - Visit https://wpml.org/account/sites/ and delete the existing site key. - Create a new site key. - Return to Plugins -> Add New -> Commercial on your website. - Click the register link and use the new site key to register WPML again. For the second issue, we advised the client to: 1) Take a full backup of the site and database. 2) Deactivate all plugins except WPML. 3) Switch to a standard theme like 2024. Then, recheck for the problem. If it persists, we suggested trying the WPML Troubleshooting Options available at https://wpml.org/documentation/support/wpml-troubleshooting-options/.
If these steps do not resolve your issues, or if they seem 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. For further assistance, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are using the THEMECO PRO theme with the CORNERSTONE sitebuilder and facing an issue where button URLs on your translated pages do not automatically link to the translated content. Although in-text links translate correctly, the button URLs revert to the original language after updates.
Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Create a backup of your site. 2. Navigate to WPML -> Settings -> Custom XML Configuration tab. 3. Paste the following code:
<wpml-config><cornerstone-widgets><widget name="button"><fields><field type="Button" editor_type="LINE">anchor_text_primary_content</field><field type="Button: Link URL" editor_type="LINK">anchor_href</field></fields></widget></cornerstone-widgets></wpml-config>
4. Save the changes. 5. Edit the original button text and button URL and translate again. 6. You will now be able to search and translate the links in ATE using the search option.
This solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: You are trying to use a different domain for your NZ site, but it is showing as not valid due to an active redirect to the .com.au domain. Solution: We recommend you remove the redirect. You should be able to access a file like https://ecotank.co.nz/license.txt without being redirected for the domain to save as valid. For more information on configuring DNS settings for different domains per language, please refer to our guide: How to use WPML with different domains per language.
If this solution does not resolve your issue or seems irrelevant due to being 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: The client is unable to display the WPML translation link in a conditional menu on their development server. While the main menu shows the translation link correctly, the conditional menu does not. Solution: We recommend adding the language switcher to the conditional menu by navigating to WPML > Languages > Menu language switcher and selecting the second menu to add the language switcher. If this does not resolve the issue, try adding the language switcher to the footer by using the Footer language switcher option. For detailed guidance, refer to our documentation on setting up language switchers: Language Switcher Options.
If these steps do not solve your problem, or if the solution seems outdated or irrelevant to your case, please 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, you can always contact us through the WPML support forum.
Problem: The client is trying to translate a Woocommerce coupon on their website. Solution: We recommend not setting coupons as translatable because they are unique for each shop and not based on language. However, if you decide to translate them, you should go to WPML -> Settings -> Post Type Translation and change the coupons' translation preference.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also highly recommend checking related known issues here, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, you can contact us directly through our support forum.
Problem: The client has translated their website into Polish, but the Polish shop page is not functioning correctly, while the regular shop page works fine. They are using the Divi theme with WooCommerce. Solution: If you're experiencing issues with your Polish shop page not functioning correctly while using Divi and WooCommerce, it's essential to ensure that the WooCommerce Multilingual & Multicurrency plugin is active and properly configured. This plugin is crucial for the WPML to work correctly with WooCommerce. We recommend reading and following our guide on setting up WooCommerce Multilingual & Multicurrency, which you can find here: https://wpml.org/documentation/related-projects/woocommerce-multilingual/.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please do not hesitate 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, you can contact us directly through our support forum.
Problem: After upgrading to PHP 8.3.x, you are encountering a PHP Deprecation notice on Toolset Types 3.5.2. The notice indicates that the return type of OTGSToolsetCommonUtilsRecursiveDotFilterIterator::accept() should either be compatible with FilterIterator::accept(): bool, or the #[ReturnTypeWillChange] attribute should be used to temporarily suppress the notice. Solution: We recommend disabling the debug mode in WordPress to prevent these warnings from being displayed to your visitors. This can be achieved by editing your wp-config.php file and ensuring it includes the following line:
If this solution does not resolve your issue or seems irrelevant due to being 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing issues with the WPML plugin on their website. The pages were barely translated, and the layout was disrupted. Additionally, there was a database error indicating a missing table: 'cuorehub_WPQ6E.staging_yBB_icl_strings'. Solution: We resolved the issue by making adjustments in the WPML settings and editing the pages: 1. Navigate to WPML-> Settings-> Custom Fields Translation section. 2. Set the "mfn-page-items" field to "Translate". 3. Save the changes. 4. Edit the page in the default language. 5. Add 'V2' to the title and update the page. 6. Remove the 'V2' and update the page again. 7. Update the translation. We advised the client to apply steps 4 to 7 for each page to ensure proper translation.
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. Additionally, 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 also visit our support forum at WPML Support Forum.
Problem: You are developing a site using Elementor with WPML and want to auto-translate links in Elementor icon list items. Despite setting a glossary for the link and resending the page to auto translation, the link remains untranslated. Solution: 1. First, edit the translation of the page. In the Advanced Translation Editor (ATE), use the search option at the top left to find the URL. You can search for the entire URL or just a part of it. For more details, see Translating links with Advanced Translation Editor. 2. If the above step does not resolve the issue, follow these steps: - Go to WPML -> Settings -> Custom XML Configuration tab and paste the following code:
- Press the Save button. - Modify the original page slightly and press the Update button. - Update the translation via WPML's Advanced Translation Editor. - Re-open the translated page to check if the links are now translated.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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 was unable to translate certain texts into Arabic, including the word 'SHOP' and phrases in the top bar of their website. Additionally, Arabic characters in the Slider Revolution were displaying backwards and separated. Solution: For the Slider Revolution issue, we recommended accessing WP Admin -> Slider Revolution and editing the 'Demo-rtl 1' slider used for Arabic. The client should remove the text layers and add them again without applying animation effects that break the words into individual letters. For the text in the top bar, which is managed by the 'Thim Elementor Kit' plugin (not WPML-compatible), we attempted standard methods to find the text through string translation but were unsuccessful. We offered to download a clone/snapshot of the website to further investigate how the plugin manages this text. For the image accordion issue, we made the fields translatable by adding custom XML configuration to the WPML settings. The client should open the page in the default language, make a minor edit to refresh the elements detected by WPML, and then proceed with the translation.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to add the site key in the OTGS installer but cannot register the key. Solution: If you're experiencing this issue, we recommend you first go to your WPML.org account profile and remove the key generated for the site you are attempting to register. Then, navigate to Plugins->Add new->Commercial tab in your WordPress admin. Here, either unregister WPML or register WPML and click on "Get a key for this site". This action will automatically generate a new key code for your site.
Please note that this solution might be irrelevant if it's 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 the issue 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
