Problem: The client is experiencing an issue where string translations are not showing on the front-end when the string checker is disabled. They have tried solutions from other tickets without success. Solution: 1. We recommended updating WordPress and all plugins to ensure compatibility and resolve any potential conflicts. 2. We advised the client to check the WPML -> String Translation section to ensure that strings related to the theme are correctly translated and that no multiple text domains are causing conflicts. 3. We suggested installing the Contact Form 7 Multilanguage addon to help with translating contact forms.
4. The issue was resolved by adding the correct text domain to the styles.css file of the theme (as it was showing two different ones on WPML -> String translation).
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 the problem persists, please open a new support ticket.
Problem: The client is experiencing an issue where a SQL query sorts posts by a custom meta field 'trainings_display_date_start' on the homepage. This works correctly on the non-translated (English) page, but not on the translated page, resulting in no posts being returned. Solution: 1. Ensure that the 'trainings_display_date_start' is copied over to the translated posts so there is meta data to sort by. 2. Include a meta query that returns only posts with a start date and then sort by that start date. 3. Verify that the posts are translated and published in the second language. 4. Test the issue with the WP default theme and only WPML plugins enabled to see if the issue is caused by something else.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 contact our support forum at WPML support forum.
Problem: If you're experiencing issues where related posts in the API still appear in the original language despite having translations, and your code works locally but not on the live site. Solution: We recommend you follow these steps: 1. Navigate to WPML-> Languages. 2. Select 'Different languages in directories' in the Language URL Format section. 3. Save your changes. 4. Resave the permalinks. 5. Check the translated endpoint with '/en/'.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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, you can also visit our support forum at WPML 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: Sie möchten Medien automatisch mit Deepl übersetzen lassen, aber die Übersetzungen können nur manuell angepasst werden, da das Media Translation Plugin die Bildmetadaten im benutzerdefinierten Block Ihres Themes nicht registriert. Solution: Wenn Sie das Theme selbst entwickelt haben, empfehlen wir Ihnen, unsere Dokumentation für Entwickler zu überprüfen, um sicherzustellen, dass die Bildmetadaten korrekt für die Übersetzung registriert sind. Besuchen Sie:
Wenn die Metadaten korrekt registriert sind, werden sie im Advanced Translation Editor von WPML verfügbar sein, und Sie können sie automatisch in Bulk übersetzen.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: WPML Support Forum.
, instead of the name of the layout, causing your code to break after translating your site with WPML, this might be due to missing custom fields in the translation. Solution: We recommend checking if the custom field settings were configured after the page was translated. If so, you can trigger the translation by modifying the original page, updating it, and then saving the translation again. This should ensure that
get_row_layout()
returns the correct layout names. Remember to update the page translations if there are other pages affected.
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 for further assistance.
Problem: The client installed WPML on their development website. While the default language displays correctly, the translated version of the website appears broken, with issues in layout, untranslated navigation menus, and other text elements. Solution: First, we addressed the navigation menu issues in both the header and footer. We recommended translating the navigation menus following the detailed instructions provided here: https://wpml.org/documentation/getting-started-guide/translating-menus/. For custom menu links and header buttons, we suggested manual translation methods as shown in this screen recording: https://go.screenpal.com/watch/cZj1bZV91yB. Additionally, to fix styling issues, we inserted custom CSS code into WP > Appearance > Customize > Additional CSS:
If you're experiencing similar issues, we recommend trying these steps. However, if these solutions do not resolve your problem or seem 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 issues persist, we highly recommend opening a new support ticket for further assistance.
Problem: The footer of your website is no longer being translated into English and French, and the associated translation strings are not found. Solution: If you find that the footer of your website is no longer being translated, we recommend checking the translation of the footer block. We have updated the translation for the page with the ID in the WPML String Translation Tool. You can check this by clicking here.
If this solution is outdated or does not apply to your problem, we recommend opening a new support ticket. We also recommend checking the page with known issues (https://wpml.org/known-issues/), verifying the version of the permanent solution, 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/de/forums/forum/support-in-german/.
