Problem: The client is attempting to translate the authors page in English using WPML and String Translator on a DIVI theme with Yoast Premium. Although some parts of the page are translated, others are not showing up as translated despite being processed in String Translator. Solution: We recommend translating the template used for the authors page, as it appears to be created using DIVI. It's essential to ensure that all parts of the page are included in the translation process. 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 open a new support ticket at WPML support forum.
Problem: The client is experiencing a critical error when activating WPML on their newly acquired WordPress site. They also need to activate the WPML subscription under their own account without losing existing translations. Solution: 1) To diagnose the issue, enable the WordPress debug mode by editing the
Then, attempt to activate WPML again and check the
debug.log
file in the '/wp-content/' directory for any errors. 2) To transfer the WPML subscription to your account, unregister WPML from the previous owner's WPML.org account and register it under your account. This process will not affect the functionality of plugins or translations.
If these steps do not resolve your issue or if the information provided becomes outdated, 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. Should the problem persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is trying to translate the block-based cart and checkout pages in WooCommerce while maintaining the new design. However, the Finnish translation is not working, and the pages remain in English, whereas other languages translate without issues. Solution: We recommend changing the locale settings to match the translation file. This can be done by navigating to the WPML languages settings page in your WordPress admin area. Here is a step-by-step guide: 1. Go to your WordPress dashboard. 2. Navigate to WPML > Languages. 3. Adjust the locale settings to match your Finnish translation files. After making these changes, your Finnish translation should work correctly, and you can maintain the new design of the block-based pages.
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 for further assistance.
Problem: If you're experiencing issues with the WPML plugin after installation, such as needing a full account restore, and you wish to remove a domain from your WPML account and reclaim the credits, follow these steps. Solution: 1. To remove a domain from your WPML account, visit https://wpml.org/account/sites and remove the key associated with the domain. This action will free up space for a new domain. 2. To reclaim credits, we have already moved 15,000 credits back to your WPML.org account.
If this solution does not apply to your situation, 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 was manually translating a page on their site, which they had done successfully for over 1,500 pages. However, one specific page was not displaying its content in the translation, showing only the title, SEO fields, and URL. The client tried deleting the translation and starting over, as well as updating the content to force a content recheck. They installed the WPML String plugin, but it did not resolve the issue. Eventually, the client created a new page from scratch, duplicated the content, and translated it successfully. Solution: We noticed that the client was using a Blog license, which lacks additional addons for page builders and automatic translation. We recommended upgrading the license to CMS to use automatic translation features and ensuring all plugins are updated to the latest versions. For manual translation, especially with page builders like Elementor, we advised following the specific guidelines provided in our documentation: https://wpml.org/documentation/plugins-compatibility/elementor/translate-elementor-site-wpml-multilingual-blog/
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 issues persist, please open a new support ticket at our support forum.
Problem: You are experiencing issues with reviews being posted in the wrong language section on your e-commerce site. Previously, you had to delete and repost the review in the correct language, which is not ideal. Solution: We recommend enabling a feature that allows reviews to be displayed in all languages. You can activate this option by checking the appropriate checkbox. For more details, please visit: Displaying Product Reviews in Multiple Languages. Once this feature is enabled, you can translate the reviews using WPML → String Translation. Reviews will then show a "(translated)" label when viewed in another language.
Please note that this solution might not be relevant if it's 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 is unable to preview translated drafts and receives an error message stating 'Sorry, you do not have permission to preview drafts.' This issue occurred after debugging the plugin when automatic translation got stuck. Solution: We recommend checking the 'Auto login to other domains' option on the WPML -> Languages page. This setting is necessary when using different domains per language. After enabling this option, please log out and then log back in to see if the issue is resolved.
If this solution does not apply to your case, or if it seems outdated, 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. Should the problem persist, please open a new support ticket.
Problem: The client reported that featured blog post images are not attached to the posts after translation. The image title and alt text are translated correctly, but the image itself isn't displayed on the page. Solution: We advised the client to ensure that the 'Duplicate Featured Image' checkbox in the Languages box is checked when editing the original post. This action does not duplicate the actual file but creates an entry in the database for the secondary languages, allowing the image to appear in the translated posts. If the client prefers not to use the WPML duplicate functionality due to concerns about database size, they will need to seek a custom solution.
Please note that this solution might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket.
Problem: You are working on a site under development and are having trouble with language settings not staying as configured. Solution: We recommend going to Appearance → Menus and ensuring that you have translated the menus into other languages. If the menus are already translated, edit each language menu to ensure the correct link/page is set. For detailed guidance on translating menus, visit Translating Menus.
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 open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with translations not moving from 'in progress' to 'completed' status despite being 100% complete in the advanced translation manager. Additionally, cancelled translations revert to 'pending' status after reloading the page. Solution: First, we installed WP Adminer and removed the translations attached to the templates with element ID = null, which seemed to be corrupted. We then duplicated the templates and edited them independently, which resolved the issue. Secondly, we set the site to minimal settings with only Elementor and WPML plugins active and a default theme. We cancelled the in-progress jobs via WPML -> Translation Management, edited the original language by adding a space, and saved the changes. This process was repeated for each language, and the translations then moved to 'completed' status. We recommend trying these steps on any other pages, templates, or posts that are stuck. If the problem persists, it might be due to a conflict with the theme, especially if using a child theme.
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 using the Astra theme and experiencing issues where multiple fields, including a button in the header and HTML fields in the footer, change languages unexpectedly. Even after disabling plugins and caching, the issue persists, and changes are overwritten when you publish them in the Astra footer builder. Solution: We tested your site by deploying it to a local environment without disabling any plugins, and the issue did not occur, which suggests a potential caching problem. Although you mentioned disabling caching, it's possible that server-level caching might still be active. We recommend checking with your hosting provider to ensure all forms of caching are thoroughly disabled. If the problem continues, it might be due to an outdated solution or a different issue not covered here. 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 these steps do not resolve the issue, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is using the Blocksy theme and attempting to add a custom information table to the WooCommerce product page using a hook. While the default language works fine, the translations made using WPML do not appear on the site. Solution: First, ensure that the hooks are set to be translatable in WPML. This can be done by navigating to WPML > Settings > Post Types translation and making the Hook post type translatable. More details can be found here: Translating Custom Posts. Next, if the hook is used in the customizer, it's necessary to specify where WPML should apply the translation of the hook. This involves going to WPML > String Translation, clicking on 'Translate texts in admin screens', and searching for the post ID of the hook in the default language. Once found, ensure it is included in string translation. Then, add the corresponding post ID for the translated language. Detailed guidance on this process can be found here: How to Translate Theme Options. If these steps do not resolve the issue, we recommend opening a new support ticket. It's also advisable to 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, please contact us through the WPML support forum.
Problem: You are trying to remove WooCommerce's strings from the database using the 'Remove strings by domain' feature, but it has no effect. Even though you receive a success message, the strings remain in the database. Solution: 1. The 'Remove strings by domain' feature only deletes untranslated strings. If the string is translated, it won't be affected. 2. To delete strings manually, go to String Translation, select the WooCommerce text-domain, and delete the strings. You can show all results using the "Strings per page:" filter below the strings table. 3. If you need to remove strings directly from the database, use the following SQL queries:
DELETE FROM wpif_123_icl_strings WHERE context = 'woocommerce';
DELETE FROM wpif_123_icl_string_translations WHERE string_id IN (SELECT id FROM wpif_123_icl_strings WHERE context = 'woocommerce');
Please note that this custom code is a courtesy and is not officially supported by us. Before applying it to a live site, please test it in a staging environment.
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 https://wpml.org/forums/forum/english-support/.
Problem: If you're using the Astra Page Header with WPML and notice that the right menu does not appear in the head section when the Astra Page Header is active, the issue might be due to the handling of custom fields. Solution: 1. Ensure that the custom field holding the menu information is set to be translated rather than copied. You can follow the steps in this guide to configure the translation settings for custom fields: Translating Custom Fields. 2. Increase the WordPress memory limit to at least 128MB, as recommended by WPML. You can do this by adding the following code to your wp-config.php file:
Add this code above the line /* That's all, stop editing! Happy blogging. */. You can verify the current WordPress memory limit in the WPML -> Support section.
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.
Problem: You are trying to add a name term to the glossary but receive a red warning message when attempting to do so. The issue does not occur in incognito mode. Solution: We recommend checking if the issue persists under the following conditions: 1. Deactivate all plugins except for WPML to see if there is a conflict with another plugin. 2. Switch your theme to a default WordPress theme like Twenty Twenty to determine if there is a conflict with your current theme. Additionally, check for any errors in the browser console when adding the term and try using a different browser or incognito mode again to see if the issue persists.
If these steps do not resolve the issue, it 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 continues, please open a new support ticket at WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive