Problem: You are trying to translate the checkout page on your WooCommerce site using WPML, but WPML does not find the string for translation, and Loco Translate cannot translate them. Solution: We have identified this as a known issue. We recommend checking the following errata page and applying the suggested workaround: https://wpml.org/errata/woocommerce-multilingual-cart-page-strings-not-translated-when-using-blocks/
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 for further assistance at WPML support forum.
Problem: You are using WPML on your website and encountering a file name mismatch error that prevents proper connection to wpml.org for updates, despite having registered the plugin and confirmed outgoing connections with your hosting provider. You are concerned about losing existing translations. Solution: We recommend enabling WordPress debugging to better understand the issue. Here are the steps you should follow: 1. Edit your wp-config.php file and add the following lines before the comment /* That's all, stop editing! Happy publishing. */:
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 WPML support forum for further assistance.
Problem: The client was unable to see the translated string 'Estimated delivery: 2-4 days' on the front end, despite having translated it in the WPML String Translation Manager. The issue was related to the shortcode content not being properly registered or translated.
Solution: 1. We advised the client to search for the string 'Estimated delivery: 2-4 days' in the WPML String Translation and ensure all instances were added and translated. 2. We suggested clearing the cache after verifying the translations. 3. We requested access to the site to further investigate the issue, identifying that the shortcode [estimated_delivery] was not pulling data in a way that WPML could automatically recognize. 4. We provided a code snippet to wrap the HTML string in a gettext call, which would allow WPML to register the string for translation. This involved defining a text domain and using WPML's hooks to register and translate the string.
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: You are trying to activate automatic translation in WPML but encounter an issue stating that you need to map your languages, despite having already done so. Solution: 1. Navigate to WPML -> Settings -> Translation engines section, activate at least one of the translation engines, and save the changes. 2. Go to WPML -> Languages -> Languages section, click on the Edit languages link, and ensure all languages are correctly mapped in the last column on the right. Click on the 'Save' button. 3. Double-check if the issue has been resolved.
If this solution does not resolve your issue or seems 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. If the problem persists, please open a new support ticket at WPML support forum.
Problem: You are trying to translate the pricing page to Spanish, but it is not working, and you receive an error message indicating that WPML failed to translate the page three times. Solution: 1. Increase the WordPress memory limit to at least 256MB. You can do this by adding the following line to your wp-config.php file:
Add it above the line /* That's all, stop editing! Happy blogging. */. You can verify the updated memory limit in WPML -> Support. 2. After increasing the memory limit: - Edit the page in the original language. - Make a small change in the content. - Save the changes. - Go to WPML -> Translation Management. - Select the page and send it for automatic translation or assign it to yourself for translation. - Translate or update the page translation and save the changes. - Check if the issue has been resolved.
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 the problem persists, please open a new support ticket.
Problem: The client wants to create a page in the Filipino/Tagalog language on their site, but Filipino/Tagalog is not available as a default language option in WPML. Solution: We recommend adding Filipino/Tagalog as a custom language either during the initial setup wizard or later. Detailed instructions on how to do this can be found here. Please be aware that automatic translation into/from Tagalog is currently not supported.
If this solution does not apply to your situation, 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 if you need further assistance. You can do so at WPML support forum.
Problem: The client is experiencing issues with WooCommerce strings displaying in incorrect languages, particularly after integrating with WooCommerce PayPal Payments. Strings that should be in specific languages are defaulting to English or showing up in random languages. Solution: If you're experiencing similar issues with string translations showing in incorrect languages, we recommend the following steps: 1. Identify and delete any incorrect strings that are not in the default language (English in this case), and ensure only the English strings are present. 2. Translate these English strings into the desired languages manually within WPML. 3. Avoid forcing re-registration of strings unless absolutely necessary, as this can cause strings to revert or duplicate in unintended languages.
This solution might not be applicable if the details or versions have changed, or if it doesn't match 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 enabled the 'Translate Everything' feature on their WPML site, resulting in high costs and inaccessible pages for monitoring credit usage. They were unable to see the translations they paid for and could not disable the feature without causing site issues. Solution: We recommended disabling the 'Translate Everything' option to control what to send for translation better. Instead, use the Translation Management dashboard (WPML -> Translation Management) to manually send items for translation. This approach helps monitor and manage translation costs and processes more effectively. For detailed guidance on managing translations, visit Translating Your Contents.
If the solution provided here does not resolve your issue or seems outdated, we highly recommend checking related known issues at WPML 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: After migrating from Wordpress.org to Wordpress.com, the full suite of WPML options is not visible in the backend, and accessing 'Translation Management' results in an error message stating 'Sorry, you are not allowed to access this page.' This issue may be related to the domain registration and site key in WPML settings. Solution: If you're experiencing this issue, we recommend that you first check if the domain for your site is correctly registered under your WPML account. Here are the steps to follow: 1. Visit https://wpml.org/account/sites and remove the current URL. 2. Add the URL back to generate a new site key. 3. Navigate to your WordPress dashboard, go to Plugins -> Add New -> Commercial, and click the link to unregister WPML from your site. 4. Enter the new site key to re-register WPML.
This process should resolve the issue with missing WPML options and access errors. If the problem persists or if this solution does not apply to your case, 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. We highly recommend opening a new support ticket if needed.
Problem: You are unable to delete deactivated languages in WPML on your site. Solution: We recommend following the steps to remove a language as outlined in our FAQ. First, visit the guide on how to completely remove a language from your site: https://wpml.org/faq/how-to-completely-remove-a-language-from-your-site/. If you encounter any issues during this process, please ensure you: 1. Have a backup of your site. 2. Disable all other plugins, leaving only WPML plugins active. 3. Switch to a WordPress default theme. 4. Check if the issue persists. If after these steps the problem remains, 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 the problem continues, please open a new support ticket at WPML support forum for further assistance.
Problem: You've added a second language to your site using WPML, but are experiencing issues with link translations not updating in the header/footer menus and on images, despite working correctly on buttons. Solution: We recommend checking the 'Adjust IDs for multilingual functionality' option in WPML -> Languages -> Make themes work multilingual. Ensure this option is checked and then save the settings. This should resolve the issue with the header and footer links not translating.
If this solution does not apply to your case, or if it seems outdated, please visit related known issues and verify the version of the permanent fix. Also, 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 for further assistance.
Problem: The footers, which appear to be widgets, are not translatable. Solution: For translating the Widget Group title, follow these steps: 1. Navigate to WPML -> Settings -> Custom XML Configuration (tab). 2. If the field is empty, paste the following XML code:
If the field is not empty, then paste the relevant part within the
<wpml-config></wpml-config>
tags. 3. Click the Save button. 4. Go to WPML -> Translation Management and look for the Block section. 5. Select the relevant Widget and send it for translation.
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 at WPML support forum.
Problem: The client is experiencing an issue where the Advanced Translation Editor is blank after restoring their site and re-registering their site key. The error log indicates 'Api error missing resource: No sitekey found for this website'. Solution: We first verified that the Advanced Translation Editor is functioning correctly by attempting to translate pages, which did not show any issues. We then suggested that the client record a screen recording of the issue using Loom. Upon further investigation, it appears to be a browser-related issue. We recommended that the client disable any browser extensions or try using a different browser to see if the issue resolves.
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 the problem persists, please open a new support ticket.
Problem: You are experiencing deprecated warnings related to sitepress-multilingual-cms and a critical error message stating 'There has been a critical error on this website' when the wp-config is turned on. Solution: The issue might be due to the PHP version compatibility with WordPress. We recommend downgrading to PHP 8.3 or lower as WordPress is not yet fully compatible with PHP 8.4. You can check the compatibility details here: WordPress PHP Compatibility.
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 WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket with us for further assistance.
Problem: You are trying to translate a custom post type project using WPML's Advanced Translation Editor, but the translated versions of these posts are redirecting to the homepage even after being marked as complete and published. The original French version works fine. You suspect a plugin conflict as WPML debug tool reports 38 third-party plugins, and WPML mentioned compatibility issues with some plugins. Solution: If you're experiencing this issue, we recommend checking your WPML settings. Under WPML > Settings, you can find the Translated documents options. Here, you can choose whether translated posts should be published automatically or saved as drafts. This setting is crucial as saving them as drafts is useful if someone on your team reviews translations before publishing. For further assistance, please visit our support forum at WPML Support Forum.
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, do not hesitate to 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