Problem: The client is using Elementor Pro and WPML to manage a multilingual site with a custom post type (CPT) called 'Chargers.' They need to apply two templates: Template A as the default and Template B with SEO blocks only for certain chargers in German. However, Template B is displaying for all languages instead of just German. Solution: We recommend creating separate templates for each language. Here are the steps to follow: 1. Set Template A for all chargers excluding the specific ones intended for Template B, ensuring it works in the default language without WPML. 2. Apply Template B only to the specific chargers intended, and verify it functions correctly. 3. For languages other than German, recreate Template B to mimic Template A, and for German, maintain the SEO blocks as desired. For further guidance on managing templates with different languages, we suggest checking out this documentation: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, please 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, visit our support forum at WPML Support Forum.
Problème : Les textes et liens des boutons ne se traduisent pas, certains contenus ne s'affichent pas dans la langue correcte, les redirections de langue ne fonctionnent pas correctement, et il est impossible de traduire certains éléments comme les champs de formulaire et les filtres de recherche. Solution : 1. Pour les problèmes de traduction des textes et liens des boutons qui ne se traduisent pas, cela peut être lié à un problème de mémoire PHP. Nous recommandons de faire une petite modification sur la page d'origine (comme ajouter un espace à la fin du titre) et de sauvegarder, puis d'éditer la traduction pour que les segments manquants apparaissent. 2. Si le texte ne provient pas directement de la page mais d'une 'custom query', il faudra aussi traduire le custom query. 3. Pour rendre les ancres HTML traduisibles dans les accordéons de Kadence, nous avons utilisé une configuration XML personnalisée. Voici les étapes suivies : - Aller dans 'WPML > Paramètres > Configuration XML personnalisée' - Ajouter le code suivant :
Après ces modifications, les ancres deviennent traduisibles.
Si cette solution ne résout pas votre problème ou semble dépassée, 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: The client is unable to find labels from a View created with the Advanced Custom Views Framework in the WPML String Translation. The labels were set up in a View linked to custom fields and a custom post type created using the Advanced Custom Fields (ACF) plugin. Although the labels are included in a language file generated in the child theme, they do not appear in String Translation. Solution: We recommend the following steps to make the labels from the Custom Views Framework translatable: 1) Modify one string in the View to ensure it includes a text domain. 2) Check the generated file in your child theme to see if it updates with the new string. 3) Rescan the child theme in WPML -> Themes & Plugin Localization. 4) Verify if the strings now appear in WPML -> String Translation.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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.
