Problema: Si estás ejecutando importaciones en diferentes idiomas usando cron jobs y luego asignando idiomas con WP-CLI en WPML, y notas que las URLs generadas tienen estructuras duplicadas como 'for-sale-fully-furnished-office-one-2', esto se debe a cómo WordPress maneja los slugs duplicados, no a un error de WPML. Solución: Es importante entender que el segmento '/en/' en la URL solo indica el idioma configurado por WPML y no afecta al slug del contenido. Si WordPress detecta un slug duplicado durante la importación, aplicará su lógica nativa para evitar duplicados añadiendo un sufijo como '-2'. Este comportamiento es independiente de WPML, que se encarga únicamente de la gestión multilingüe. Si deseas evitar este comportamiento, asegúrate de que los slugs sean únicos o diferenciados desde el origen antes de la importación.
Si esta solución no resuelve tu problema o si la información parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problème : Vous ne parvenez pas à être traducteur du site bien que vous soyez administrateur et vous souhaitez que les pages ne se synchronisent pas automatiquement avec l'original. Solution : Pour dissocier la page de traduction de l'original, utilisez l'option « traduire indépendamment ». Cela empêchera la page de se synchroniser avec le contenu original, résolvant ainsi les problèmes de traduction lors des modifications via l'éditeur de votre site. Cette fonctionnalité est détaillée ici : Documentation WPML. Si vous avez déjà des traductions CSV, nous vous recommandons d'utiliser directement l'éditeur WordPress. Pour une solution personnalisée permettant de cliquer sur « traduire indépendamment » en masse, un plugin MU spécifique peut être installé. Avant toute manipulation, assurez-vous de créer une sauvegarde de votre site. Placez le fichier PHP dans le dossier /wp-content/mu-plugins (créez-le si nécessaire). Une nouvelle option apparaîtra dans WordPress > Outils > WPML bulk translate independently, permettant de dissocier les pages en masse.
Si cette solution ne s'applique pas à votre cas ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de confirmer que vous avez installé les dernières versions des thèmes et plugins, et de contacter notre support pour assistance sur le forum de support WPML.
Problem: The client needed editors to access more WPML features, specifically the glossary function, without elevating them to Translation Managers. Despite being registered as translators, editors were unable to access or modify the glossary. Solution: We clarified that by default, editors do not have access to all WPML features. To allow editors to translate content, they must be added as translators via WPML->Translation Dashboard->Manage Translators & Services, which the client had already done. This setup enables editors to translate assigned content or initiate translations directly from pages or posts. However, for editors to access and manage the glossary, they must be assigned as Translation Managers. This role will allow them to update, add, or remove glossary items. The glossary itself automatically applies during translations in the Advanced Translation Editor, providing accuracy and context without direct editor intervention. For more details on managing glossary entries, visit How to Create and Manage Glossary Entries.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with receiving translations on the ACF Options Page when using GraphQL. They attempted to select a preferred language using GraphQL queries but were unsuccessful. Solution: We recommend using our official WPML addon for GraphQL, which can be found here: WPML GraphQL. Currently, it is not possible to use GraphQL with ACF Options Pages. We have noted this as a feature request for a future version and have added the client's vote to it.
If this solution does not resolve your issue or seems outdated, please check the 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 the problem persists, we highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client is concerned about translating synonyms from Yoast SEO Premium in WPML's Advanced Translation Editor for better SEO across different languages. Solution: We clarified that the synonyms entered in Yoast's custom fields are used internally for calculating SEO scores and do not appear on the site or influence search engine indexing directly. Therefore, translating these synonyms in WPML will not affect your SEO as they are not visible to search engines. For effective multilingual SEO, focus on translating the main content and key phrases for each language, rather than the synonyms.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Also, check the related known issues, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
