Problem: The client wants to translate their website from Dutch to English using WPML and is seeking advice on the best translation option considering SEO and Google Ads. Solution: We recommend considering your priorities when choosing a translation method: 1. Translate Automatically: Saves time but may require review to ensure translations meet your brand’s standards. 2. Translate Myself: Offers full control over translations, ideal for tailoring content for SEO. 3. Duplicate Content: Useful for maintaining content structure, though it demands extra SEO optimization for English. A hybrid approach, starting with automatic translation and refining key pages manually, might also be effective. Don't forget to utilize the WPML SEO add-on for enhanced compatibility with SEO plugins. More details can be found here: https://wpml.org/documentation/related-projects/wpml-seo/
If this solution does not fully address 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 open a new support ticket or visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are experiencing issues with automatic translations still occurring despite having disabled them in the settings, and this has resulted in the unintended use of translation credits. Solution: First, ensure that in WPML > Settings, you have selected the "translate what you choose" option. Next, navigate to WPML > Settings > Post Types Translation and verify that there is no "translate automatically" option selected for the post type in question. It's possible that the translation jobs were sent for automatic translation before these settings were adjusted, which might explain why translations are still being processed automatically. If you wish to reclaim the credits used, you can click to take back the credits if you do not want the automatic translation functionality.
If this solution does not resolve your issue or seems outdated, we 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. Should the problem persist, please open a new support ticket with us.
Problem: The client is trying to delete images from their multilingual WordPress site to free up space. They have deleted images from the English media library, but the images remain in the media libraries of other languages. The client is unsure if they need to delete the images from the FTP server or if each image gets duplicated for each language. Solution: We recommend enabling the option in WPML > Settings to 'delete translations when deleting a post'. This setting ensures that when you delete an image from the default language, it also deletes the entries in other languages, effectively removing the file completely from the server. Images are not duplicated across languages; there is only one file with multiple database entries for different languages. If this option was not enabled when you initially deleted the images, you would need to manually delete them from the other language libraries. For future deletions, having this setting enabled will streamline the process by removing images from all languages simultaneously.
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 for further assistance.
Problem: The client is developing a multilingual website and wants to know if it's possible to set up translations with languages as parameters and later switch to different domains for each language upon launch. Solution: We confirm that it is possible to start with one URL format, such as 'Language name as a parameter', and switch to 'A different domain per language' at launch. The translations will remain intact regardless of the URL format change. For more details on language URL options, please visit https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/.
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 https://wpml.org/forums/forum/english-support/.
Problem: You want to translate media links in the image gallery widget from Ultimate Addons for Elementor, but the links still point back to the default language even after translating the page. Solution: We recommend checking if the 'custom link' field added by the Ultimate Addons for Elementor plugin is available for translation. Here’s how you can proceed: - Navigate to WPML > Settings > Custom Field Translation and check if there's a 'custom link' field. If it's there, change the translation preference for that field to 'Translate'. - Go to Media > Library and click on the image to which the link is attached. - Select 'Edit more details'. - Once the image detail page has loaded, switch to the secondary language using the language switcher on the top bar. - Enter the custom link you want to display in the other language and save the changes.
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 further assistance is needed, please open a new support ticket at WPML support forum.
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/.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
