Problem: You are trying to translate new listings and update translations of old listings, but the Advanced Translation Editor (ATE) is not loading. Instead, you see a spinning wheel with a message: 'Unable to retrieve job details.' Solution: We have confirmed that all systems related to the ATE are now functioning correctly. However, there might be a short delay as the system processes a backlog of accumulated jobs. We recommend trying to access the ATE again now. If you continue to experience issues, please check the related known issues and verify that you have installed the latest versions of WPML and its extensions. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so here: WPML support forum.
Problem: After updating the WPML translation plugin, you are unable to translate messages. Clicking the translation icon leads to a screen that continuously reloads without allowing translations. Solution: We recommend you test the translation again. There has been an update that should resolve this. If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If problems persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client manually installed a new WPML update because it wasn't showing in the WordPress updates section or in plugins, which resulted in a critical error on the website. Solution: We logged into the site and attempted to update the WPML plugins via the Plugins -> Add New -> Commercial page. However, the site was still pointing to localhost, which we identified from the WPML -> Support page notice indicating the site was detected at localhost. This could interfere with updating plugins from a publicly mapped address.
To resolve this, we deactivated all plugins, switched to the standard WP theme 2025, updated the WPML plugins (WPML, String Translation, and WCML), and then reactivated these along with WooCommerce. After these steps, the fatal error was no longer present.
We recommend the client to try reproducing the issue with the current setup and report the steps if the error reoccurs. Additionally, we advised using PHP 8.2 until newer versions are fully supported, as PHP 8.4 is still in beta support by WordPress. For more details on PHP compatibility, visit WordPress PHP Compatibility.
If this solution does not resolve your issue or seems outdated, 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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: You are trying to translate a product using WPML, but after recent updates to WPML Multilingual CMS and WPML String Translation, the Advanced Translation Editor (ATE) does not display. Instead, the spinner turns infinitely, and you receive an error message indicating that it takes longer than usual. Solution: We have confirmed that all systems are now functioning correctly again. However, there might still be a short delay as the system processes a backlog of accumulated jobs. We recommend trying to translate again now and checking if the ATE displays correctly.
If this solution does not resolve your issue or seems outdated, please visit our known issues page to check for any related known issues. Also, ensure you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at our support forum.
Problem: The client needs a comprehensive guide on translating taxonomies and WooCommerce pages using WPML, especially when automatic translation does not meet their specific needs. They encountered issues where taxonomies were not automatically translated when translating products, leading to incorrect category assignments.
Solution: 1. Taxonomies will be translated automatically along with the posts or products they are assigned to. If you're experiencing different results, we recommend checking your site's settings and providing us with WPML debugging information. More information here: https://wpml.org/de/faq/provide-debug-information-faster-support/
2. For WooCommerce pages, replace any WooCommerce Blocks on the Cart or Checkout page with WooCommerce Shortcodes, as we currently cannot translate new blocks. You can find more about WooCommerce Page Shortcodes here: https://woocommerce.com/document/woocommerce-shortcodes/page-shortcodes/ Strings from these pages can then be translated using WPML > String Translation.
3. Attributes are translated automatically with the product they are assigned to. To translate all global attributes in one job, create a product, assign all available attributes to it, and send the product for automatic translation.
4. If a taxonomy is already translated, it will be synced when translating the post. You can also sync taxonomies at WPML > Taxonomy Translation if WPML recognizes that taxonomies are missing on translated posts.
If the solution provided here 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: If you're experiencing issues with the English version of your page not displaying, specifically on the rooms page, and encountering a 404 error similar to the one discussed in the WPML forums, we have a solution that might help. Solution: We recommend the following steps: 1. Navigate to WPML → String Translation. 2. Remove the translation for the Accommodation slug from String Translation. 3. Go to WPML → Settings. 4. Retranslate the Accommodation slug.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 if needed. You can do so at WPML support forum.
Problem: The client is experiencing an issue where the post carousel is not displaying on the Japanese translated pages of their website. The posts are of a custom post type called "projects". Solution: We discovered that all Japanese posts were set as drafts. After publishing these posts, they were properly assigned to their respective categories, which resolved the issue and the post carousel now appears correctly on the Japanese pages. If you're experiencing this issue, we recommend checking the status of your posts in the translated language and ensuring they are published and correctly categorized.
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 problem persists, please open a new support ticket.
Problem: You are setting up WPML for the first time and have enabled translation for custom post types created with the ACPT plugin. However, when these are enabled, the Translation Management page crashes Solution: First, ensure that the custom post types are compatible with WPML. Although not officially tested by our team, the ACPT plugin, has developed an integration with WPML. You can find more details here: https://docs.acpt.io/integrations/wpml
But you need to make sure that the 'hierarchical' parameter for your custom post types is explicitly set to either true or false during registration. If this parameter is omitted, it may default to null, causing the error.
If these steps do not resolve your issues or the solution seems outdated, 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. If problems persist, we recommend opening a new support ticket at our support forum.
Problem: If you're using WPML with WooCommerce and have enabled automatic translation, you might encounter an issue where duplicating a published WooCommerce product causes it to start translating immediately, even though you want the duplicated product to remain as 'drafts' and not be translated until it is published. Solution: Currently, there isn't a direct option in WPML to prevent automatic translation for duplicated products that are still in 'draft' status. A potential workaround is to disable automatic translation for the product post type until the product is ready to be published. 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 more personalized assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with ACF link titles not being translated on your website, it might be because the ACF link fields are set to "Copy" by default. This setting ensures that internal linking works automatically but prevents the translation of the link text. Solution: We recommend setting the field group to "Expert" mode and changing the link field to "Translate". After making these changes, edit the link field on the original content, save the page or post, and then update the translation. This should allow the ACF link titles to be translated.
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: You are trying to add yourself as a translator in the WPML plugin, but the system cannot find your user account. Solution: 1. We might need to install a database management plugin like Adminer to access and modify your user profile directly in the database. 2. The issue usually stems from incorrect capabilities assigned to your user account. Specifically, there might be an incorrect and broken capability entry in your user’s database record. 3. After fixing the capability entry in the
_usermeta
table for your account, we can manually add you as a translator for the desired language pair.
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.
Problem: The client has added a language switcher to the header of their WordPress site using WPML and wants the secondary and tertiary languages to be visible immediately upon landing on the homepage, without needing to click a drop-down arrow. Solution: If you have added the language switcher block, you can change its layout in the template where you added it. For detailed instructions, please refer to our documentation here: https://wpml.org/documentation/getting-started-guide/language-setup/language-switcher-options/#add-language-switcher-template. Additionally, you might find this screencast helpful: https://www.loom.com/share/6be801c66f3c44049ca47b657f6850b6?sid=b71b4d2d-138b-436a-a7a5-a83819873070. If these steps do not resolve your issue, or if the solution 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client has a multilingual WooCommerce site and needs to use different SKUs for products translated into Latvian, without losing the language switcher functionality. The client also inquired about managing SKUs in different languages using WPML. Solution: We explained that in WPML, product translations must share the same SKU to sync stock and prices effectively across different languages. To use different SKUs, the client would need to create separate, original products for each language, which would not be linked as translations and thus would not support the default language switcher functionality. However, the client can create a custom language switcher or button that links to the respective products in different languages. We also provided links to documentation for further customization using hooks:
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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: You are trying to translate the homepage of your site using WPML, but while subpages translate correctly, the homepage does not translate using either URL format (https://sites.com/?lang=es or https://sites.com/es/). Solution: We recommend you follow these steps: 1. Provide debug information by following the instructions here: https://wpml.org/faq/provide-debug-information-faster-support/ 2. Navigate to your Dashboard > Pages. 3. Open the edit screen of the original page and look for the "Languages" section in the sidebar options. 4. Make a minor change, such as adding an extra blank space at the end of a sentence or paragraph. 5. Save the changes. You should see a circular arrow beside the links for the second language, indicating that an update is required. 6. Edit the translation again and ensure it is saved as 100% translated. If the problem persists, please inform us about how the homepage was created, specifically if any page builder was used.
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 continues, please open a new support ticket at WPML support forum.
Problem: The client is working on a site under development and needs guidance on which editor to use for editing a translation after importing it from XLIFF. The client uploaded an XLIFF file for a translation from English to Italian. After uploading, the translation appears on the frontend, but some segments still need translation. However, in the Advanced Translation Editor (ATE), all segments appear empty. Solution: We recommend using the Classic Translation Editor (CTE) for editing translations imported from XLIFF files. Unlike ATE, CTE supports the display of HTML markup and can handle XLIFF imports effectively. ATE, designed to run on an external server with a different code base, does not support these features and only displays pure text. If you are using XLIFF import/export, CTE is the appropriate tool as it is compatible with XLIFF files and supports markup language.
Please note that while new features for CTE are not anticipated, it will remain available in future versions of WPML as many clients rely on it. There are currently no known issues with using XLIFF files in CTE, which you can verify at known issues.
If this solution does not resolve your issue or 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. If further assistance is needed, 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
