Problem: The 'read more' button on the Testimonials and Blog pages is not translating. Solution: If you're experiencing issues with the 'read more' button on your site, we recommend following these steps to potentially resolve the issue: 1. Navigate to WPML → String Translation. 2. Enable the option 'Look for strings while pages are rendered'. 3. Visit the page where the 'read more' button is not working. 4. Return to WPML → String Translation and check if the string for the 'read more' button has been registered. 5. If found, translate the string accordingly. For more detailed guidance, please refer to our documentation on finding and translating strings.
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.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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, you can also contact our support team directly at https://wpml.org/forums/forum/english-support/.
Problem: The client moved their site to a new hosting and changed the domain from test.jinshiyuan.sg to delightsip.com. After the move, WPML detected the new address as the old one, causing issues with site recognition. Solution: If you're experiencing this issue after moving your site to a new hosting, we recommend you follow these steps: 1. Click on YES in the message box regarding the site address change. 2. Set the website to not share credits. 3. Visit your WPML account and remove the existing keys at https://wpml.org/account/sites/ 4. In your website's admin panel, go to Plugins > Add New > Commercial Tab and remove the key. 5. Create a new key for your current domain (delightsip.com) at WPML.org. 6. Register the new key in the same location in your admin panel (Plugins > Add New > Commercial Tab). For more detailed instructions, you can check https://wpml.org/faq/how-to-remove-the-this-site-is-registered-on-wpml-org-as-a-development-site-notice/
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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: If you're experiencing issues with the WPML translation editor not recognizing line breaks in posts created through the Classic Editor, where instead of seeing different translation zones for each paragraph, you see one big paragraph, we can help. Solution: We are currently working on a permanent fix for this issue in future releases. In the meantime, to address this for previously created content, you need to delete the existing translation and recreate it. Here’s how you can do it: 1. Ensure you have a full website backup. 2. Navigate to your Pages or Posts tab. 3. Change the language in the topbar by clicking on the flag and selecting a secondary language. 4. Find the translation, send it to the trash, and then permanently delete it from the trash can. By following these steps, when you create a new translation, it should adhere to the new settings and resolve the issue. If this solution does not resolve the issue, please visit this documentation.
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 developing a site and trying to translate the 'add to cart' button but cannot find the relevant code in functions.php, despite following documentation. Solution: If you're experiencing this issue, we recommend checking our documentation on string registration to make the strings available for translation in the UI. Here are some useful links:
Please note that the 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 experiencing issues with losing translations of accordion content in DE/FR/IT languages when updating your homepage using WPML. Additionally, module IDs lose their translations when the page is updated. Solution: We have attempted to replicate the issue using a clean Sandbox environment with only WPML and Divi, using the imported homepage layout from your site. In this controlled environment, updating the title did not affect the translations in the Divi Accordions, suggesting the issue might be specific to your installation. We recommend providing us with a Duplicator copy of your site for further debugging.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
