Problem: You are trying to translate the 'Contact Us' button in the header of your site using WPML, but despite translating the strings as per previous instructions, the button remains untranslated. Solution: We recommend following these steps to ensure the string is correctly registered and translated: 1. Navigate to WPML → String Translation. 2. Enable the option 'Look for strings while pages are rendered'. 3. Visit the page where the untranslated 'Contact Us' button appears. 4. Return to WPML → String Translation and check if the string has been registered. 5. If found, proceed to translate the string. For more detailed guidance, please refer to our documentation on finding strings that don't appear on the String Translation page. If the issue persists, please provide us with screenshots showing how you added this button.
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 continues, do not hesitate to open a new support ticket at WPML support forum.
Problem: You are developing a real estate agency website using the Easy Property Listings plugin and want to translate property listings without using POEdit. You have enabled the automatic translation feature but are unable to translate the property content. Solution: First, navigate to WPML -> Settings -> Post Types Translation. Here, ensure that all post types related to the Easy Property Listings plugin are set to 'Translatable' instead of 'Not Translatable'. This adjustment will allow you to translate the properties content directly using WPML. For detailed guidance, please refer to our documentation on translating custom posts: Translating Custom Posts.
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: WPML Support Forum.
Problem: The client needed to reset the translation memory for the Spanish language to apply a less formal tone to translations, but was concerned about affecting other languages. Additionally, there was uncertainty about whether the linking between their development site and main site to share the pay-as-you-go account and translation memory was functioning correctly. Solution: We escalated the issue to our developers who successfully reset the translation memory specifically for the English to Spanish language pair without affecting other languages. This allowed the client to translate content with the desired less formal setting. We also ensured that the client was kept informed throughout the process via email updates and direct communication in the support ticket.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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 https://wpml.org/forums/forum/english-support/.
Problem: The client reported multiple PHP deprecation notices related to WPML after updating to PHP 8.2. These include deprecated property creation for WPML_LS_Menu_Item. Solution: We informed the client that these issues are already addressed in the upcoming WPML version 4.7, which is in the final QA stage. Meanwhile, we recommended a workaround involving a site backup and following the steps provided in a related support ticket: https://wpml.org/forums/topic/deprecated-errors-with-php-8-2/#post-15994511.
To prevent these warnings from displaying to site visitors, we advised disabling the debug mode in WordPress by adding
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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.
Problem: You are trying to translate the 'lees meer' button on your website but cannot find where to do this. Solution: If the 'lees meer' button is part of the theme or plugin files, or if it appears on options pages, you can translate it using the WPML >> String Translation page. If the button was added through a page builder, you should translate it via the WPML Translation Editor when translating that page into another language.
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 this solution does not apply to your case, or if it seems outdated, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was facing an issue where some posts translated from Dutch to English using WPML were not visible on the frontend of their website. The client discovered that changing the theme resolved the visibility issue of the translated posts. Solution: We recommended the client to ensure they are using WPML Advanced Translation Editor and to follow these troubleshooting steps: 1) Increase the WP Memory Limit to 256MB. 2) Open the problematic post in the original language, make a minor edit, and save the changes. 3) Update the post's translations. 4) Clear all types of caches. 5) Resave the settings under Settings>>Permalinks. Additionally, we suggested performing further troubleshooting if the issue persists: - Clear the cache in WPML. - Remove ghost entries from the translation tables. - Fix element_type collation and other database-related issues using the WPML>>Support page's Troubleshooting options. - Enable WP_DEBUG to collect error logs if necessary, and share them for further analysis.
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 at WPML support forum.
Problem: The client was experiencing issues with WPML after migrating their site from Flywheel to WPEngine. Specific problems included errors in loading translation jobs and engines, and issues with completing translations for new pages. Solution: We recommended checking the REST API dependencies as detailed in our documentation here: https://wpml.org/documentation/support/rest-api-dependencies/. Additionally, we adjusted the site address in the WordPress settings from 'https://www.wastewaterscan.org' to 'https://content.wastewaterscan.org' to resolve the issue.
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: You have translations completed for your site, but some products and pages do not display the translation even though the status indicates they are translated. Specifically, the language dropdown does not display the languages even though the page is translated. Solution: First, ensure that the translated products are published and not in draft status. You can do this by navigating to Products -> All Products, then switch the language from the top admin bar to ensure that the translated products are published.
If this solution does not resolve your issue, or if it seems outdated or not applicable to your case, 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 contact us through our support forum at WPML support forum.
Problem: You are experiencing an issue where the language switcher is not opening the translated page on your website. In the WordPress editor for the English page, the link to the German page is correctly listed. Solution: First, ensure that the translated page is published and not in draft status.
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 continues, please do not hesitate to open a new support ticket with us for further assistance. You can do so at WPML support forum.
Problem: The client has translated the homepage but the main menu does not appear on the translated page. Solution: 1. Navigate to WPML > Support > Troubleshooting. 2. Click on the buttons as shown in this screenshot: https://prnt.sc/LiF_4ictWpW5 3. After completing the process, synchronize the Menu by following the instructions in this guide: https://wpml.org/documentation/getting-started-guide/translating-menus/#easy-customizable-wp-menus-sync 4. Ensure the header 'New Header' is set as translatable under WPML > Settings > Post Type. 5. Go to WPML > Translation Management, find 'New Header', and send it for translation. Complete the translation in WPML > Translation menu.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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: The client is experiencing an issue where translations start a new line for each sentence on their website. This problem seems to be related to the theme being used. Solution: We recommend the following steps to address the issue: 1) Switch to the Hello Elementor theme. 2) Update the page in the original language to refresh the translation settings. 3) Update the translation using the WPML Advanced Translation Editor. Additionally, consider increasing the WP Memory Limit to 256 MB as per the minimum requirements for WPML, which can help with processing and performance issues. For more details on increasing memory limits, please visit WPML minimum requirements and Increasing memory allocated to PHP.
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 at WPML support forum.
Problem: The client is experiencing issues with incomplete translations on their website, despite translating strings and plugins. Specific examples include placeholders and certain strings like 'Remember Me' not being translated into Romanian. Solution: 1. For PHP strings, such as placeholders modified in the theme's
functions.php
, ensure the correct use of translation functions. Replace
icl_translate()
with
__()
for compatibility with WPML's String Translation. 2. After modifying the code, translate the string using WPML's String Translation tool. For detailed guidance on translating PHP strings, visit Translating the Theme You Created. 3. For strings added via Elementor, directly edit the translated page using Elementor to ensure all texts are translated.
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.
Problem: You've translated the strings for the footer, but when switching languages on the front end, the footer texts do not change despite trying several cleanup services. Solution: Please follow these steps: 1- Copy the footer template ID. 2- Go to WPML-> String Translation. 3- Scroll down and click on the "Translate texts in admin screens »" link. 4- Search for the ID. 5- Select the string. 6- Click on the "Add to String Translation" button. 7- Then click on the "« Return to String Translation" link. 8- Translate the ID to the translated template ID. For more detailed guidance, please check our guide on translating texts in the admin texts screen.
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 needed, please do not hesitate to open a new support ticket for further assistance.
Problem: The client was facing issues with product category and tag links not correctly displaying in French and German versions on their multilingual website. Despite resaving permalinks and adjusting WPML settings, the links would revert to English or not direct correctly. Solution: We advised the client to manually translate the links by editing the homepage translations and searching for "HTTP" to ensure all links are translated. This approach resolved the issue. It's important to note that while WPML attempts to adjust internal URLs automatically, in some cases, such as with shortcodes or Elementor widgets, manual translation is necessary. For further guidance on translating links, visit this link.
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.
Problem: You are trying to display a translated profile field in a different section than the default Profile section on your website. Specifically, you have moved the field to the 'Profile header' using custom code, but the field displays in English instead of the selected language. Solution: To ensure the field displays in the correct language, you should use the
wpml_translate_single_string
hook instead of the
wpml_object_id
filter, as the latter is intended for filtering post types by ID. Here is how you can modify your code:
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Also, 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 visit our 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
