Problem: The client experienced a PHP memory limit error during the installation of WPML and the String plugin, which led to a site crash. After resolving the initial crash by renaming and deleting plugins, the client faced issues with missing database tables and persistent PHP memory errors when JetEngine was activated. Solution: 1. Deactivate JetEngine to prevent PHP memory limit errors. 2. Upload and install WPML plugins. 3. Reactivate JetEngine after the installation. This sequence helps manage the PHP memory load during WPML installation. If you're experiencing similar issues, we recommend trying these steps. Additionally, ensure your hosting environment allocates sufficient memory, as outlined in our minimum requirements.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please check our known issues page and confirm that you have the latest versions of themes and plugins installed. If problems persist, we highly recommend opening a new support ticket here.
Problem: If you're experiencing issues connecting your .ar (Argentine) domain with WPML because the system does not validate it as an Argentine domain, Solution: We recommend that you uncheck the 'validate' box and save the WPML options. Ensure that your domain is configured correctly. If so, it should work fine without needing validation.
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: The client is trying to add Argentine (Spanish) and Taiwanese languages to their WordPress site using WPML, but these specific language options are not available by default. Solution: To add custom languages in WPML: 1. Navigate to WPML → Languages. 2. Click on 'Edit Languages'. 3. Scroll down and click 'Add Language'. 4. Enter the details for the custom language and save. For more detailed guidance, please visit: Editing WPML's Languages Table
If you are setting up languages per domain, ensure that: 1. Your domains are configured to show the same website without redirections when WPML is disabled. 2. Re-enable WPML and select the 'language per domain' option. If it doesn't validate, uncheck the box and save. For additional help, see: Language Setup
Note: The 'hreflang' attribute is used only for loading translation files and does not affect other website functionalities. If issues persist, consider resetting the language settings in WPML > Support > Troubleshooting > Reset Languages option.
Please be aware 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 problem persists, please open a new support ticket at WPML Support Forum.
Problem: When using SEOPress plugin with WPML, the product archive slugs are not correctly translated in the XML sitemaps generated by SEOPress.
Solution: We have acknowledged the issue with SEO Press not correctly handling translated slugs in sitemaps. We recommend checking the following errata for a workaround and subscribing to the comments on our errata page for this specific issue to stay updated on future fixes: https://wpml.org/errata/seopress-product-archive-slug-not-translated-in-sitemaps/.
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 with us for further assistance.
Problem: The client is developing a site and using WPML to streamline the translation workflow. They have a custom field to set a menu on a specific post type and want the same menu on translated pages without needing to translate the menu name or set it manually each time. They are experiencing issues with unnecessary translation requests for some values. Solution: We explained that there isn't a specific option to control this behavior directly when it's set to 2, as the ACF translation is activated regardless of the input provided. We suggested using the "Different fields across languages" option, which allows translating the input method directly as a string. For more details, see the documentation on translating ACF field labels with WPML.
If this solution does not apply to your case, 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.
Problem: The client reported that Download Monitor files, which were set to be translatable using WPML, stopped working correctly due to a recent update. The update removed the appending of the language code to the URL of downloads, causing a routing issue. Solution: We recommended adding a PHP snippet to the client's child theme's functions.php file or using a plugin for adding PHP snippets. The code to add is:
This snippet helps fix the home URLs. Additionally, we advised the client that the Download Monitor plugin is not officially compatible with WPML. We suggested contacting the plugin author to inquire about compatibility or joining our GoGlobal program for assistance in making the plugin compatible. More information on our GoGlobal program can be found here: GoGlobal program.
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 is unable to translate certain parts of the new WooCommerce checkout block using WPML, specifically the strings stored in JSON files which do not translate through the usual String Translation interface. Solution: Please ensure that WooCommerce is updated to the latest version, as version 9.2.3 includes updates that might resolve translation issues on the checkout 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are using WPML > String Translation to translate contents from an Option page created with Jet Engine, aiming to update data on various pages like the homepage on a Spanish website. While you can translate the labels, the values remain in the default language. Solution: We recommend using the standard string translation method to translate these option values into English. You can find a detailed guide on how to do this by following this link: guide.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to translate the WooCommerce Gateway descriptions and titles using WPML, but despite the strings appearing in String Translations, they still display in the main language (German). Additionally, the client is experiencing issues with the Quick Edit functionality in English and different translation masks for shop products. Solution: We recommend resaving the default language settings or fields to ensure that the translations are correctly reapplied. It is essential to use the WooCommerce Multilingual plugin, as it is necessary for WooCommerce to function correctly with WPML. If you're experiencing issues with specific parts of the plugin or its functionality, we suggest opening a new support ticket to discuss possible workarounds.
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 do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to delete all content for a particular language using the instructions from https://wpml.org/faq/how-to-completely-remove-a-language-from-your-site/, but the process is slow and the number of assets decreases only slightly. Solution: If the number of assets is decreasing, even slowly, it indicates that the process is working. The speed of deletion depends not on WPML but on your hosting/server resources. We recommend disabling all other plugins temporarily to see if this speeds up the process. Additionally, consider contacting your hosting provider to discuss upgrading to a more robust hosting package. Please be aware of a known issue where taxonomies are not deleted when using the 'Delete content from database' option, detailed here: https://wpml.org/errata/taxonomies-are-not-deleted-with-the-delete-content-from-database-option/.
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.
Problem:
The client is experiencing 500 Internal Server Errors on translation pages (/ru and /en) when WPML Multilingual CMS is active. The issue persists despite disabling other plugins, updating permalinks, and checking .htaccess configurations.
Problem: The client was unable to reassign credits from live websites back to available credits in their WPML account. Solution: We advised the client to unregister WPML using the old keys and then re-register it with new keys. Here are the steps we recommended: 1. Visit https://wpml.org/account/sites/ and remove the current site key. 2. Generate a new key for each site. 3. Go to the website's backend, navigate to Plugins > Add New > Commercial, and unregister WPML from the old key. 4. Re-register WPML using the new key. 5. Follow the steps outlined in https://wpml.org/documentation/automatic-translation/how-to-assign-automatic-translation-credits-to-your-sites/ to add credits to each site.
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: If you're trying to translate products on your site using WPML and find that clicking the + icon from the 'All Products' page leads you to the translation queue instead of the advanced translation editor, this summary is for you. Solution: We recommend you follow these steps: 1. Make a complete backup of your site. 2. Navigate to WPML → Support and click on the Troubleshooting link. 3. Click 'Synchronize local job IDs with ATE jobs' and 'Synchronize translators and translation managers with ATE'. If this does not resolve the issue, proceed with the following steps: 1. Go to WPML → Translation Management → Translators tab. 2. Add your user account as a translator and assign the language pairs. 3. Check if you can now use the Advanced Translation Editor.
If the solution provided here 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 these steps not resolve your issue, please do not hesitate to open a new support ticket at our support forum.
Problem: If you're unable to find and translate the placeholder text 'Search entire site' to French in your WPML setup, even after trying to enable auto-register strings. Solution: First, ensure that you scan your theme files for strings that might not appear on the WPML String Translation page. You can find detailed instructions on how to do this here: Scan the Theme or Plugin. If the string still doesn't appear, you might need to access the 'Translating Strings From Admin and Settings' section to add the string manually to String Translation. Detailed steps can be found here: Translate Admin and Settings Strings. Lastly, if the strings appear reversed in different language versions of your site, ensure that you have correctly assigned the languages to each string in the WPML String Translation interface.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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 use a variable within functions.php in a custom shortcode for your WordPress site, but the text within the variable is not being recognized by WPML for translation. Solution: The strings you are attempting to translate are not following the WordPress localization standards, which is why WPML cannot register them for translation. To resolve this, you need to modify your code to adhere to these standards. Here is how you can update your code:
_e( 'Congratulations! Shipping is on us :', 'my-theme' )
_n('Free delivery on orders of %s or more.', wc_price( $min_amount ), 'my-theme' )
After updating, ensure to perform a full site backup. Then, scan the theme for the strings to translate by following the instructions here: Scanning the theme or plugin.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
