Problem: The client is attempting to translate an article using WPML but encounters an issue where some text elements remain in English because they are not available for translation. The client questions why some core blocks are not available for translation and how to ensure all text elements are translated. Solution: We recommend the following steps to ensure all text elements are picked up and translated: 1. Send the page for translation or update the existing translation: * Go to WPML → Translation Dashboard in your WordPress admin. * Use the filters to find your article. If the issue persists, it might be due to the use of emojis or specific characters that are not supported by the current database collation. In such cases, changing the database collation to "utf8mb4_unicode_520_ci" might resolve the issue. Additionally, consider manual translation for pages with complex designs or frequent changes, as detailed in our documentation on using different translation editors for different pages.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: You are trying to translate an Elementor page with image sliders, but one image is shown twice and another is ignored in the translated version. Solution: 1. Ensure that you have updated WPML to the latest version and check if the issue still persists. 2. Edit the home page in the default language, make a minor edit, and update it. 3. Use the WPML translation editor to update the translation and check if the images now appear correctly on the translated page.
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/.
Problem: The client is developing a site using WPML for automatic translation and faces issues with gender-specific translations defaulting to the feminine form. Additionally, the client needs support for Swiss German, which is not available in the current translation options. Solution: 1. For gender-specific translations, switching from DeepL to WPML AI is recommended. WPML AI allows for specifying the gender by summarizing the site’s content accordingly. 2. Regarding the support for Swiss German (de_CH), which does not use the 'ß' character, although DeepL does not support this variant, we can explore enabling it through WPML AI. This would involve running tests to assess if the desired quality can be achieved, as it has not been implemented due to a lack of client requests.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum.
Problem: When translating a block theme, specifically the 'Header' template and 'Navigation Menus', some URLs in the secondary language do not update with the language code and translated slug, while others link to the primary language without a language prefix. Solution: First, ensure that when using the WordPress block 'Custom Link', you include the entire URL for the link, not just the slug (e.g., /articles). After updating the URL, resend the 'Navigation Menu' for translation. This should make the URL field appear correctly in the translation interface. It's important not to use the Site Editor to edit the Navigation in a second language. Instead, always use the Translation Management and translate the Navigation with the WPML Translation Editor. Here's how: 1. Go to WPML > Translation Management > Dashboard. 2. If 'Click filters' is visible, click it to see all the site's content. 3. Create a job for your Navigation Menu and access it at WPML > Translations. 4. When translating the navigation, you can translate the links on the WPML Translation Editor.
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. We highly recommend opening a new support ticket if the problem persists. For further assistance, visit our support forum at WPML Support Forum.
Symptoms:
When translating the 'header' template part, there are no strings found. Additionally, my block theme has only 1 header template part, but there are 3 listed under the 'Template Part' section in 'Translation Management'.
Questions:
What am I missing when translating the 'header' template part since no strings are found?
Why are there 3 header template parts listed under 'Template Part' in 'Translation Management' when my block theme has only 1?
Solution:
Under "Translation Management" is a section "Navigation Menus". For some reason I thought this was for classic themes and ignored it. Turns out that this is very Navigation Block menus live. The name "Main Menu" is set per default in the Block Editor Inspector Sidebar under "Advanced" (when editing the Navigation Block), which was the reason why I got confused.
