Problem: The client needed to split the language switcher into two columns, but the CSS code that worked in 2019 was no longer effective due to changes in the code. Solution: We recommended the following CSS to split the language switcher dropdown items into two columns:
.wpml-ls-legacy-dropdown .wpml-ls-sub-menu {
width: 140px;
}
.wpml-ls-legacy-dropdown ul ul .wpml-ls-item {
float: left;
width: 70px
}
If this solution does not apply to your case, or if it seems outdated, we encourage you to check the 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. Should you need further assistance, please do not hesitate to open a new support ticket in our forum: https://wpml.org/forums/forum/english-support/.
Problem:
Can I hide products that are not translated, in both the original and in the secondary language?
Solution:
You can't control how many products show up in the default language but you CAN control how many products are showing up in the translated version of the site.
So, in the secondary language, you should be able to display only the translated ones and in the source/original language, you can show all of them.
If you would like to accomplish that, please follow the steps below:
- Go to WPML -> Settings and click on "Post Types Translation"
Ask the hosting support to whitelist any block on this behalf and further make sure that the minimum requirements for running WPML are met in the server.
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.
