Problem: The client reported that certain strings have been translated but the translated content is not visible in the front end. Solution: We recommended the following steps to ensure the strings are properly translated and visible: 1. Navigate to WPML-> Theme and plugins localization, select your theme/plugin, and scan. 2. Go to WPML-> String Translation. 3. Scroll down and click on the "Translate texts in admin screens »" link. 4. Search for the needed strings. 5. Select the strings. 6. Click on the "Add to String Translation" button. 7. Then click on "« Return to String Translation" link. 8. Translate the strings, clear the cache, and check the front end. For more detailed guidance, please refer to our documentation on translating texts in admin screens: Translating texts in admin screens.
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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem:
Single sentence with line is split in Advanced translation editor as separate segments
Solution:
An HTML line break placed between two phrases is considered as two separate lines based on the language grammar and the same is applied by ATE. it is not an issue but an expected behavior
Problem: The client was trying to uninstall WPML from their website. After deleting all pages and following the support troubleshooting instructions, the website's database crashed. Solution: If you're experiencing this issue, we recommend the following steps: 1. Go to Plugins -> Installed Plugins and deactivate all plugins, leaving only WPML enabled. 2. Navigate to WPML -> Support -> Troubleshooting page, check the 'I am about to reset all translation and language data.' option, and click on the 'reset and deactivate WPML' button. 3. Return to the Plugins screen and delete the WPML plugins. This process should not cause any problems or crashes on your website. It's likely that there was a conflict with another plugin causing the database crash. Ensure you have a complete website and database backup before proceeding.
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.
Problem:
The client had a different font on his translation than his original content.
Solution:
The issue here was related to Cross-Origin Resource Sharing because the client configured the languages to be on different domain names.
Adding the code from the link below in the htaccess allow to get the font from a different domain.
Problem:
Navigation menu is not displaying for translated language page.
Solution:
Enabled translations for the header and footer. Then, translating the header and footer fixes the navigation missing issue on translated language page.
Problem: The client reported that after changing background images on a few translated pages, those translations reverted to the default English language. The editor on those pages appeared different, showing the Classic Translation Editor with a warning, specifically on the About page and Brake discs page.
Solution: 1. We confirmed that the client was seeing the Classic Translation Editor and suggested that if they need to remove elements on the translated pages, they should disable the WPML Translation Editor. 2. We advised the client to use manual translations by editing directly in Elementor for the secondary language, as they would for the default language. This approach allows for more flexibility and control over the translations. For detailed instructions, we provided a link to our documentation: Using different translation editors for different pages.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly 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. If you still need assistance, please do not hesitate to open a new support ticket with us.
If you are using Elementor Pro or a different theme with customizable theme options, you may want to set a different logo per language.
Once you translate the logo, you may need to tell WPML which logo to display on the front-end in each language. You can do this by going to String Translation and translating the logo ID. If you cannot find the logo string in String Translation, you may need to click the Translate texts in admin screens link at the bottom of the page and add the text to the String Translation table.
Problem:
The client wants to translate the text added using the CSS "content" property.
Solution:
Sorry, you can’t translate strings from the CSS section/file using the WPML >> String Translation page. However, You can use the ‘:lang’ selector before other selectors to use different CSS for different languages.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 need further assistance, please open a new support ticket: Contact WPML Support.
Problem:
Unable to add glossary with hidden languages
Solution:
Under your site Dashboard, go to Users > Profile, Or you can go to Users > All users, Select a User to edit there you can set the "Display hidden languages" and save.
Problem: If you are trying to translate your categories and notice that the slug is automatically changed to [category]-en and it seems strange, and you are wondering if changing it back without the -en could affect your site. Solution: By default, WordPress does not allow having two categories with the same slug, so WPML adds the language code at the end. However, WPML allows you to bypass this restriction if you edit the slug manually, which it sounds like you've already done. Therefore, you can use the same slug in different languages for your translated categories.
If the solution provided is not relevant to your case, because it could be outdated or simply not applicable to your situation, we recommend open a new support ticket. We also suggest that you review the known issues, check the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If you need more help, do not hesitate to contact us at the WPML support forum.
Problem: The client is encountering a database error indicating a duplicate entry '0' for the primary key when trying to save a translation. This error suggests that AUTO INCREMENT may be deactivated on the database table.
Solution: 1. Check the
icl_translation_status
table in the database to ensure that AUTO INCREMENT is enabled. 2. If AUTO INCREMENT is not enabled, it needs to be activated. This may also require checking other WordPress tables like
wp_options
,
wp_posts
, and
wp_users
to ensure they have AUTO INCREMENT enabled where necessary. 3. If there is an entry with '0' in a table where you are trying to enable AUTO INCREMENT, you must remove that entry before you can enable AUTO INCREMENT. 4. Always ensure you have a recent and working backup before making any changes to the database.
Please note that this solution might not be relevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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.
Problem: If you're unable to translate certain texts that appear in the Customize and Front end sections of your site, it might be because these strings have been recognized but not yet associated with the String Translation panel. Solution: We recommend visiting WPML>>String Translation and clicking on the Translate texts in admin screens » link at the bottom of the page. Then, search for the missing strings in the Admin Texts Translation screen to see if they are listed. If you find them, please add them for translation. For more detailed guidance, refer to our documentation on Finding Strings that Don’t Appear on the String Translation Page.
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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing two issues: first, imported XLIFF translations are visible on the front-end but not within the Advanced Translation Editor (ATE). Second, the Mega Menu breaks after synchronizing menus with WPML. Solution: For the XLIFF import issue, we explained that translation services rely on the Classic Translation Editor (CTE) and it is expected that translations will not be visible in the ATE nor editable there. To resolve this, we recommend disabling the ATE in the WPML translation editor options by navigating to WPML -> Settings. Switching to the CTE may serve as a workaround. Regarding the Mega Menu issue after WPML Menus Sync, we would need more information to provide a specific solution. If you're experiencing similar issues, please note that the solution provided might be outdated or not applicable to your case. We highly 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. If the problem persists, please open a new support ticket with us for further assistance.
The properties CPT are set to ‘Translate automatically’ in WPML -> Settings. The properties were imported using WP All Import. Nevertheless, nothing happened. The properties were not automatically translated.
Solution:
Imported posts (any post type) can not get automatically translated. This is expected behavior. To get the imported posts translated automatically, you need to go to Translation Management and send the imported posts to translation.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
