Problem: You are experiencing a loss of metadata, specifically translator comments from XLIFF files, when switching from the Advanced Translation Editor to the standard WordPress editor. This issue arises after clicking "Edit anyway", causing the translation to disconnect from the XLIFF file and resulting in the loss of all translator comments. Solution: Unfortunately, it is technically not possible with WPML to maintain the
<note>
elements from XLIFF files once you switch to the native WordPress editor. Custom development would be necessary to import these
<note>
elements into WordPress metadata or to make them visible in the block editor UI. We recommend setting the translation method on the original content to "WordPress Editor" to prevent overwriting manual translations when later using the WPML Translation Editor. For more details on setting the translation method, please visit: 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that the JavaScript file 'wpgmp-project-filters.js' was not loading on their site's translated pages for German (de), French (fr), Norwegian (no), Danish (da), and Swedish (sv) languages, although it was loading correctly for English (en), Dutch (nl), and Spanish (es). Solution: Initially, we suggested clearing all caches (plugin, server, Cloudflare, etc.) to see if that resolved the issue. Upon further investigation, we discovered that the problem was due to custom code in the file
wp-content/themes/kebonyglobal/functions.php
. Specifically, the function
kebony_relocate_inline_scripts()
contained a line of code that needed commenting out:
// strpos($src, 'project') !== false ||
After making this change, the JavaScript file should load correctly on all language versions of the site.
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 problems persist, please open a new support ticket.
Problem: Vous souhaitez exclure une URL d'archive CPT pour une langue spécifique dans le sitemap Yoast, car il n'y a pas encore de traduction pour cette langue. Les contrôles Yoast SEO s'appliquent à l'ensemble du CPT, et le filtre wpseo_sitemap_exclude_post_type ne fonctionne pas pour votre cas. Solution: Nous vous recommandons d'utiliser un hook sur
wpseo_sitemap_url
. En utilisant ce hook et en retournant « false », vous pouvez exclure l'URL du sitemap. Voici un exemple de code que vous pouvez utiliser :
Ce code vérifie si l'URL contient un certain segment (dans cet exemple '/private/') et l'exclut du sitemap si c'est le cas. Vous pouvez ajuster la condition pour correspondre à votre URL spécifique.
Si cette solution ne vous semble pas pertinente ou si elle est obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent, et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: Sie haben eine Info in das Astra-Login/Register-Formular hinzugefügt und suchen den String zum Übersetzen. Sie haben bereits Strings durchsucht, Admin-Textsuche durchgeführt und auch Theme und Plugins neu gescannt. Solution: Wir haben Ihr Snippet auf unserer Entwicklungsseite getestet und festgestellt, dass das Registrieren und Übersetzen der Strings wie erwartet funktioniert. Bitte überprüfen Sie, wo Sie das Snippet eingefügt haben, ob per PHP oder über ein Plugin wie Code Snippets. Es ist wichtig, dass die Text-Domain korrekt ist und mit der Text-Domain des Plugins oder Themes übereinstimmt, von welchem die Strings geladen werden. Wir empfehlen Ihnen, uns die WPML-Informationen zur Fehlerbehebung zukommen zu lassen, um Ihnen besser helfen zu können. Mehr Informationen dazu finden Sie hier: https://wpml.org/de/faq/provide-debug-information-faster-support/
Falls diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihren Fall 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.
Problem: If you're experiencing an issue where a string is not outputting in the Estonian language and instead shows in English, despite being translated in WPML String Translation, this might be due to the text domain settings. For instance, using
esc_html_e( 'Privacy settings', 'cookieconsent' )
might not work, but changing the text domain to your theme's text domain, like
__( 'Privacy settings', 'child-theme' )
, resolves the issue.
Solution: We recommend keeping the function that outputs the string and then scanning your theme for strings. Here are the steps: 1. Keep the function:
2. Go to your WordPress Dashboard > WPML > Theme and plugins localization and select your theme to scan. 3. After the scan, navigate to WordPress Dashboard > WPML > String translation and search for the string in question. 4. Ensure the content of the string matches the flag next to it. If not, set the source language correctly by following this guide: How to change the source language of strings. 5. Complete the translation and check the front end.
If this solution does not resolve your issue or seems irrelevant due to being 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 problem persists, please open a new support ticket.
Problem: The client needed help translating custom fields such as 'Experience', 'Fresh', and 'Year' from the WP Job Board plugin, which were not registered in a way that WPML could translate them due to compatibility issues. Solution: We recommended creating the same custom fields again for the secondary language and using the manual translation method to manually assign the translated fields to the translated jobs, while keeping the original fields assigned to the default language jobs. Additionally, we suggested configuring WP Job Board so that empty field values are not displayed to avoid showing duplicate fields. We also advised contacting the plugin author for potentially better multilingual support and checking the list of officially compatible plugins at https://wpml.org/plugin/.
If this solution does not resolve your issue or seems outdated, 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.