If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: After moving to a new server and activating the WPML plugin, you are experiencing PHP warnings related to open_basedir restrictions on every page load. This issue started after the server migration, despite using WPML String Translation 3.2.18. Solution: We recommend clearing your logs and cache to ensure that no old server paths are being cached erroneously. It's also important to double-check the logs after performing these steps. If the problem persists, it might be related to specific server settings or configurations that were changed during the server migration. For detailed guidance, please refer to our documentation on this issue: open_basedir restriction issue.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: If you're experiencing issues with translating a newsletter form in the footer of your website and it's not appearing correctly, it might be due to the use of an iframe instead of a shortcode. Solution: We recommend checking your footer template to see if it contains an iframe. If so, replace the iframe with the appropriate shortcode to ensure proper translation functionality. This change was tested and confirmed to work correctly. For further guidance, you can refer to these screenshots:
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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are using a custom plugin with a custom shortcode that includes a string. After attempting to translate the string via WPML, the shortcode no longer renders on the frontend, even though it was visible on the English version previously. Solution: We recommend translating the string through WPML's String Translation. You can access this feature from your WPML dashboard. Here is a step-by-step guide: 1. Navigate to WPML -> String Translation. 2. Search for the 'Check-In Now' string and ensure it is correctly translated.
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 the problem persists, please open a new support ticket.
Problem: The client has a custom taxonomy set as not translatable, yet translations are being added to the terms. The taxonomy consists of country codes as slugs, and the client is concerned that making the taxonomy translatable will alter the slugs (e.g., 'GR' becoming 'GR-DE'), which could affect the site's geolocation functionality. Solution: We advised that while WordPress does not allow duplicate slugs for taxonomy terms by default, WPML can manage this issue. When translating a taxonomy term, the client can edit the term to remove the language prefix, thus keeping the original slug intact (e.g., changing 'GR-DE' back to 'GR'). Additionally, if the client wants the terms to be synced across translations with the English post as the source, this functionality should already be in place.
If this solution does not resolve the issue or seems outdated, or if it does not apply 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.
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.
Problem: The client updated to RankMath Pro and noticed that in RankMath Analytics, the Keywords tab only shows keywords for the Dutch version of the site and not for the German and English versions. Solution: We explained that this behavior is expected because the section displays keywords based on popularity, regardless of the keyword language or the destination URL. All data comes from the same Google Search Console tag, tracked under a single website property. To find keywords for specific language versions, use the "Search Post URL" bar at the top and paste the URL of the desired language version. Additionally, it's important to understand that Google customizes search results based on factors like browser language and search history, which can affect which keywords and pages appear in searches.
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 further assistance is needed, please open a new support ticket at WPML support forum.
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: You are trying to automatically translate media and display the alt description on a translated image, but the alt text is not translating automatically and only shows in Dutch instead of German. Solution: We recommend enabling the option to "Translate media library texts with posts" in the Media Translation settings under WPML -> Settings. Here are the steps you should follow: 1. Activate the mentioned setting. 2. Open the original page. 3. Make a minor change, such as adding a word. 4. Undo the change and save the page. 5. Open the page in the translation editor and check if the alt description appears. 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: You are trying to find where to translate the breadcrumb for the Home page on your site under development, but you are unable to locate the breadcrumb translation. Solution: 1) Follow these steps to locate and translate the breadcrumb: - Go to WPML-> Theme and plugins localization, select your breadcrumbs plugin, and scan it. - Go to WPML-> String Translation. - Scroll down and click on the "Translate texts in admin screens »" link. - Search for the needed strings. - Select the strings. - Click on the "Add to String Translation" button. - Then click on the "« Return to String Translation" link. - Translate the strings, clear the cache, and check the front end. For more detailed guidance, check our guide on translating texts in admin texts screen. 2) If you still face issues, please share your Debug information with us. You can find detailed instructions on how to provide this information here.
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 needed, please open a new support ticket here.
Problem: You are experiencing an issue where WooCommerce emails sent after completing an order are partially in the default language (NL), despite having translations available for another language (FR). This occurs even though all email texts have been translated into FR.
Solution: We have identified this as a known issue and have published a temporary workaround. We recommend visiting the errata page for detailed instructions: https://wpml.org/errata/wc-order-update-emails-may-contain-mixed-language-texts/. Additionally, subscribing to the comments on this errata page will keep you updated on any developments.
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 has translated their header and footer using WPML, but the footer is only displaying in English across different language versions of the site. Solution: We found that the footer needs to be manually selected in the "Page Settings" section for each translated page. To resolve this issue, edit each translated page and ensure that the translated footer is selected. This adjustment was made on the homepage as an example.
If this solution does not apply to your case, or if it seems outdated, 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 WPML Support Forum.
Problem: You want the translation column to always be visible on the WooCommerce product list in the admin area, but even after using a code snippet to unhide the column, no data is displayed in it. Solution: We recommend implementing a custom function to ensure the 'icl_translations' column is always visible and contains data. Here's a step-by-step guide: 1. Add the following function to your theme's functions.php file or a custom plugin:
Please test this solution in a staging environment before applying it to your live site, as this custom code is a courtesy and not officially supported by us.
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 experiencing issues with manually translated product attributes adding an extra slug in the URL, which causes filters in other languages to not work correctly, especially when using the Kadence theme with WooCommerce and the Query Loop, this summary might help. Solution: We recommend modifying the code in your Kadence Blocks Pro plugin to handle the attribute translations more effectively. Here are the steps: 1. Open the file
4. After making these changes, go to your default language product and click update to create a re-index for the loop.
Please note that this solution might become outdated or may not apply to your specific case. If this solution does not resolve your issue, 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 translating pages and have noticed that the button to save translations in the advanced editor is mislabeled in French, for the 'Save' button instead of 'Enregistrer' or 'Confirmer'.
Solution: We have incorporated the correct language labels for the save (and other) button(s) in the upcoming versions of the WPML's Advanced Translation Editor (ATE). Although there is no exact release date available at this moment, these changes will be included in the next release.
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, please 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
