Problem: The client is experiencing an issue with their site while using WPML, specifically with sharing the same headers. Solution: If you're experiencing this issue, we recommend you try the steps outlined for translating the header, which can be found here: https://wpml.org/forums/topic/header-7/#post-16851445. If this does not address your specific question, please provide more details or screenshots to help us better understand your issue.
Please note that this solution might be 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, do not hesitate to open a new support ticket at WPML support forum.
Problème : Le client utilise le plugin PublishPress et rencontre des problèmes pour afficher les blocs personnalisés dans la langue souhaitée après leur traduction. Il a d'abord traduit les blocs personnalisés avant de traduire son Custom Post Type (CPT) en utilisant l'éditeur WordPress au lieu de l'éditeur WPML. Solution : Nous avons conseillé au client de suivre une méthode de traduction cohérente. Si le client préfère les traductions manuelles, il doit utiliser l'éditeur de site et non l'éditeur de traduction WPML. Nous avons fourni une documentation pour aider à utiliser différents modèles pour différentes langues, accessible ici : https://wpml.org/fr/documentation-6/traduire-vos-contenus/comment-utiliser-differents-modeles-pour-differentes-langues/. Après avoir clarifié le processus avec une vidéo explicative, nous avons confirmé que le problème était dû à l'utilisation de méthodes de traduction mixtes pour des contenus liés. Nous avons suggéré de tester le workflow sur un thème WordPress par défaut pour éviter les erreurs critiques et d'autres conflits possibles.
Cette solution pourrait ne plus être pertinente en raison de mises à jour ultérieures ou de différences dans votre cas spécifique. Nous vous recommandons vivement de consulter les problèmes connus sur https://wpml.org/known-issues/, 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: The client is experiencing an issue where the sidebar content on translated pages always appears in English, despite using the WP Translation Editor and setting the ACF repeater field to 'Different fields across languages'. The client tried various code modifications suggested on forums, but none resolved the issue. Solution: We recommend checking the active language and fetching the correct post ID based on that language. Here is an example of how you can modify your code:
This solution is specific and may only work for a limited number of translations. If this approach does not suit your needs or if you are using a different setup, 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 for further assistance.
Problem: Du arbeitest mit dem 'Contest Gallery' Plugin und hast festgestellt, dass einige Texte für die Anmeldemaske und die Kategorien nicht in den Übersetzungs-Strings von WPML erscheinen. Trotz Aktivierung der Option 'Nicht übersetzte Zeichenketten erkennen' und dem Versuch, die Strings zu synchronisieren, sind die Texte nicht auffindbar. Solution: Das 'Contest Gallery' Plugin, insbesondere die kostenlose Version, ist nicht vollständig nach den Internationalisierungsstandards von WordPress programmiert, was zu Problemen mit WPML führt. Das Plugin registriert keine benutzerdefinierten Felder in den WPML-Einstellungen und verwendet fest codierte Zeichenfolgen ohne konsistente Textdomänen. Außerdem werden beim Übersetzen keine neuen Galerien angelegt, was bedeutet, dass die IDs der Galerien in verschiedenen Sprachen nicht übereinstimmen. Eine Lösung könnte sein, die Pro-Version des Plugins zu verwenden, falls diese anders programmiert ist. Alternativ könnten die Plugin-Autoren unser Go Global-Programm in Anspruch nehmen, um die Kompatibilität zu verbessern.
Falls diese Lösung für dich irrelevant ist, weil sie veraltet ist oder nicht auf dein Problem zutrifft, empfehlen wir dir, 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 des permanenten Fixes zu verifizieren und zu bestätigen, dass du die neuesten Versionen von Themes und Plugins installiert hast.
Problem: The client is unable to select radio choices on a translated page using WPML with Elementor. The translated form buttons are unselectable, and the default values are incorrect. Solution: The issue of unselectable form buttons was resolved in the latest WPML update (WPML Multilingual CMS 4.7.2). We advised the client to update their WPML plugin by navigating to Plugins > Add new on the Commercial tab and clicking on 'Check for WPML Updates'.
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.
Problem: The client is experiencing issues with strings not translating unless the 'AUTO REGISTER STRINGS FOR TRANSLATION' is enabled. When this option is disabled, the strings do not translate. Solution: The issue stems from the Give Plugin not loading its text domain correctly, which prevents WPML from translating the strings. This problem is due to changes in how text domains are loaded in the latest major WordPress release. We recommend contacting the Give Support Team to inquire if they are aware of this issue and to check if an update is planned to resolve it.
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 open a new support ticket with us at WPML support forum.
Problem: The client is unable to see the full text for translation in WPML, coming from Spectra blocks, and the translated text does not appear on the frontend for their product descriptions.
Solution:
1) We added necessary XML configurations for Gutenberg blocks in WPML -> Settings -> Custom XML Configuration to make them translatable. Here is the XML needed for some of the blocks:
2) We translated several related "Patterns" and "Content Blocks" via WPML -> Translation Management. After assigning the translation tasks, we completed them from the "Translation queue". 3) For any untranslated blocks, such as product tabs, additional XML paths were added, and a minor change in the original content was made to update the translations.
If this solution does not resolve your issue, 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 the problem persists, please open a new support ticket.
Problem: You are developing a site and encounter an issue where Plugin Notes Plus stops working when the WPML main plugin is activated. The specific error in the console is:
Uncaught TypeError: Cannot read properties of undefined (reading 'replace')
at various points in the Plugin Notes Plus JavaScript files. Solution: The Plugin Notes author released a fix for this 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 for further assistance.
Problem: You are working on a site under development and encountered a problem with duplicate ACF fields from different language fields. After setting all field groups to 'Same fields across languages' and removing duplicates, the data in the fields was saved for all languages in the admin. However, on the site, two out of three languages display correctly, but the third shows an error: 'Uncaught Error: Illegal offset type in isset or empty'. Solution: We recommend checking a similar support ticket that might help resolve the issue you are facing: https://wpml.org/forums/topic/fatal-error-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in-var-w/ Before making any changes, please back up your database first. Additionally, verify if the ACF options were translated in other languages using the format "%options_(language_code)_resources%", where (language_code) is replaced with the actual language code.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: You are developing a multilingual site using custom posts with custom taxonomy (CPT UI) and specific fields for taxonomy archive pages (ACF). The issue occurs on the taxonomy term 'Engines -> Hybrid', where data is not displayed on the archive page. Despite recreating it and clearing the WPML cache, the problem persists. The 'Hybrid' term does not show the contents of the custom fields on the archive page, except in German where only the background image is displayed. Disabling WPML, the 'Hybrid' terms are displayed correctly. Solution: The issue is with the UpSolution Core plugin from Impreza. We will contact the author since it is a compatible theme. The definitive solution must come from them because it is a problem with their code logic. A temporary solution is to comment out line 264 of the file
. We have done this on the staging site, and as you can see, it now works. If there are updates to UpSolution Core before this issue is fixed, you will need to repeat the modification.
Please note that this solution might be 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: When the client selects Spanish on their website, and then navigates to another page, they need to select Spanish again because the language does not persist across different pages. Solution: We recommend ensuring that the language switcher is properly configured to maintain the language selection across different pages. This might involve checking the settings for language persistence in WPML. Additionally, if the issue is specifically related to the menu not being translated, we suggest following our guide on translating WordPress menus with WPML. You can find the guide here: Translating WordPress Menus with WPML.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please do not hesitate to open 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, you can contact us directly through our support forum.
