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.
Problem: The client reported that the language switcher was not displaying correctly on their website's menu. Specifically, the switcher was not centered, and hovering over the flags displayed code instead of the expected flag and country name. Solution: We advised the client to check if the content on their pages was fully translated and published. Unpublished translations could cause the language switcher to display incorrectly. We recommended checking the WordPress 'Pages' section in the backend to see the status of translations. If a pencil icon is visible, the translation is published. An eye icon indicates the translation needs review, a gear icon suggests the translation is not saved, and a circled arrows sync icon means the translation needs to be updated due to changes in the main language.
If you're experiencing similar issues with your language switcher, we recommend following these steps to ensure all translations are complete and published. If the problem persists, it might be due to an outdated solution or a different 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 these steps do not resolve the issue, please open a new support ticket at WPML support forum for further assistance.
Problem: The client wanted to resize the flag in the menu language switcher to 8x12px and was unable to change languages using the menu language switcher. Solution: We advised the client to add custom CSS to resize the flag. The client can insert the following CSS code in the site's backend under Appearance > Customizer > Custom CSS:
img.wpml-ls-flag {max-width: 20px !important;}
This code allows the client to adjust the flag size as needed. For further customization without CSS, we provided documentation links:
Regarding the issue of the language switcher not allowing language changes, we created a separate support ticket to address this specific problem.
Please note that the solution provided might be 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.
Problem: The client needed to know how to restart automatic translations in WPML after adding new translation credits. Solution: 1. Navigate to WPML -> Settings. 2. Change the translation method to
'Translate what you choose'
and save the changes. 3. Switch the translation method back to
'Translate everything'
and save again. Upon saving, a window will appear asking what to do with the existing content. Here, you can start the automatic translation for it.
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 WPML Support Forum.
Problem: You are trying to translate all page content, including content created in Avada, but the translation editor does not include Avada fields. Additionally, you encountered a WordPress database error indicating invalid data during the translation attempt. Solution: We recommend following these steps to resolve the issue: 1. Edit the page in the original language. 2. Resave the widgets on the page. 3. Make slight changes to the page and update it. 4. Go to the translation editor; all the content should now appear, allowing you to complete the translation.
If this solution does not resolve your issue or seems outdated, please 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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client reported that icons on their website's German translation pages were displaying as squares instead of the intended icons. Solution: We identified that the issue might be related to the Cross-Origin Resource Sharing (CORS) Policy, as the client uses different domains per language. We suggested checking the browser console for any CORS-related error messages and sharing these with their hosting support to allow access to font/icon files across domains. Additionally, we recommended a potential fix involving setting the 'Access-Control-Allow-Origin' header, which can be found in detail here: WPML documentation on CORS and custom fonts.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: You have updated links in the English version of your website, but the translated versions still display the old, inactive links. Solution: We recommend using the 'Translate Link Targets' option found in WPML → Settings. If this does not resolve the issue, please follow the step-by-step guide on translating links using the Advanced Translation Editor, which can be found here: Translating Links with Advanced Translation Editor. Before making any changes, ensure to backup your database.
If this solution does not apply to your case because it might be outdated, or if you encounter further issues, 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 additional assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are unable to save a translation using the Advanced Translation Editor. When you try to save, nothing happens. Solution: We recommend checking if a link for the texts is missing in your translation setup. Adding the necessary link as indicated in the documentation might resolve the issue. If you're experiencing this, please refer to the Advanced Translation Editor documentation for detailed guidance.
If this solution does not apply because it's outdated or not relevant 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. Should these steps not resolve your issue, please open a new support ticket.
Problem: If you're experiencing issues where the auto-translated product descriptions do not maintain the original line breaks, resulting in all paragraphs merging into one, we can help.
Solution: We recommend turning off the "I prefer bigger segments" option in the Advanced Translation Editor (ATE) and then resending the product for automatic translation. Make sure to select the "Overwrite existing translations" option. This workaround is detailed in our errata page, which you can find here: https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/.
Additionally, subscribing to the comments on the errata page will keep you updated on when the issue is resolved.
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 at WPML support forum.
Problem: You are unable to save 'TBD' next to the Zulu language in the Edit Languages section. When you try to save, the screen refreshes, and the update is not saved.
Solution: We discovered that the 'Default locale' field for the Zulu language was empty, which caused the issue. To resolve this, you need to fill in the 'Default locale' field. The correct locale code for Zulu in South Africa is
zu-ZA
. You can adjust this default locale according to your needs. For more information on locale codes, visit Locale Codes Documentation.
If this solution does not apply to your case, or if it seems outdated, 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.
Problem: If you're experiencing issues with the Ninja Forms Multilingual plugin where the PDF Form Submission extension fails to export PDFs when a form includes a checkboxlist field, this might be due to a compatibility problem between these plugins.
Additionally, subscribing to the comments on this errata page will keep you updated on when a permanent fix is rolled out.
Please note that this solution might be irrelevant if it's 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: You are trying to ensure that all original text on your site is translated, but you've encountered an issue where not all text is translated, particularly with WP Bakery modules. Your theme does not include a wpml-config.xml file, despite claiming WPML compatibility. Solution: We recommend following our guide on registering WP Bakery modules for translation. You can find the guide here: Register Page Builder Content for Translation. Please try the following steps: 1. Register one module by adding the necessary code to the WPML-> Settings-> Custom XML tab. 2. Edit the page in the default language, make a minor edit, and update it. 3. Attempt to translate the page again and check if the strings appear correctly in the translation editor.
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 you still need assistance, please open a new support ticket at WPML Support Forum.
Problem: If you browse to the website without the language suffix (e.g., https://telium.io), the site renders incorrectly. This issue is likely related to how WPML handles redirection and language URL settings. Solution: We recommend checking the WPML settings under WPML → Languages → Language URL format. If you have the option 'Use directory for default language' enabled, you have two main options: 1. Uncheck the 'Use directory for default language' option. This change will allow https://telium.io/ to display the root page as intended. 2. Set up a redirect from https://telium.io/ to https://telium.io/en/ if you prefer to keep using the 'Use directory for default language' setting. You can find detailed instructions on setting up this redirect here.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
