Problem: If you're experiencing issues with the WPML translation where clicking the translate button redirects you back to the page with an authentication error, and you also encounter a 'too many redirects' error, the problem might be related to custom code in your site's functions.php file. Solution: We recommend checking the functions.php file in your website's Child Theme for any custom code that might be modifying the redirect request and causing a signature mismatch. If the issue disappears when the parent theme is enabled, this indicates that the problematic code is in the Child Theme's functions.php. You should remove the code blocks one by one to identify which one is causing the issue.
Please note that this solution might be outdated or not applicable 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. If the problem persists, please open a new support ticket at WPML support forum.
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: You are experiencing an issue where custom product tabs created in WooCommerce using the WPML and Woodmart theme display correctly in the backend in different languages, but on the frontend, the tab content appears only in the original language (Italian) across all languages. Solution: First, ensure all WPML components are up-to-date. If updating does not resolve the issue, try re-saving the original product in the backend to re-synchronize the translation data. If this still does not work, the issue might be due to the custom field used for the tab content not being configured for translation in WPML. Here are the steps to address this: 1. Go to Products → All Products and edit the original Italian product. Enable Custom Fields in the Screen Options. 2. Note the exact name of the custom field containing the tab content, such as
_woodmart_custom_tab_content
. 3. Navigate to WPML → Settings and set the translation preference for this custom field to Translate. 4. Save changes, re-save the original product, update the translation, and clear all caches. If these steps do not resolve the issue, it might be outdated or not applicable 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. If the problem persists, please open a new support ticket for further assistance at WPML support forum.
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: You want to enable browser language detection on the home page but not on other pages. Solution: We recommend implementing a custom solution using WPML hooks, as the browser language redirect option in WPML can only be enabled for the entire site. You can use the wpml_enqueue_browser_redirect_language hook for this purpose. For more hooks, please check the full list at WPML Hooks Reference.
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 you still need assistance, please open a new support ticket at WPML support forum.
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.
