Problema: El cliente estaba traduciendo su sitio web del inglés al español y siguió los pasos para traducir menús de enlaces personalizados usando la herramienta WP Menus Sync de WPML. A pesar de haber traducido las páginas, las taxonomías y haber utilizado la herramienta String Translation para traducir los enlaces personalizados, los menús en español no mostraban las traducciones y continuaban en inglés. Solución: Primero, recomendamos verificar que todos los pasos se hayan seguido correctamente como se describe en nuestra guía de traducción de menús, que puede encontrar aquí: Traducción de menús. Si el problema persiste, sugerimos crear un menú de prueba para ver si el problema se resuelve. Además, hemos informado a nuestro equipo de documentación para actualizar la guía basándose en la experiencia del cliente.
Si esta solución no es relevante para su caso, porque podría estar desactualizada o no aplicarse directamente a su situación, le recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tiene instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, puede visitar nuestro foro de soporte en WPML support forum.
Problem: Der Kunde hat Schwierigkeiten beim Übersetzen von Vorlagen, da der 'Sprache'-Reiter in der linken Sidebar fehlt, wenn er mit dem WordPress Editor arbeitet. Solution: Wir haben erklärt, dass für jeden wiederverwendbaren Block innerhalb eines Posts automatisch ein Übersetzungsauftrag erstellt wird, sofern dieser Block nicht bereits übersetzt ist oder auf einen Übersetzer wartet. Daher ist es nicht notwendig, die Übersetzung manuell für jeden Block einzeln vorzunehmen. Es sind keine Änderungen geplant, da das System der automatischen Erstellung von Übersetzungsaufträgen die Notwendigkeit manueller Eingriffe bereits eliminiert.
Falls diese Lösung für Sie irrelevant erscheint, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen außerdem, die Seite mit bekannten Problemen 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: You are experiencing a styling issue in the backend when using the Gravity Forms Multilingual addon, resulting in a broken UI. Solution: We recommend disabling the No Conflict mode in your Gravity Forms settings. This mode, when enabled, prevents third-party scripts from affecting the Gravity Forms administration pages, which can lead to styling conflicts. To disable it, edit your form settings and turn off the No Conflict mode. For more detailed instructions, visit the Gravity Forms documentation: https://docs.gravityforms.com/enabling-no-conflict-mode/
If this solution does not resolve your issue or seems outdated, please check 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 at WPML support forum.
Problem: The client is experiencing an issue where switching to the Spanish language on their website redirects them to the homepage instead of the translated Activity page. They have set up WPML and translated a custom post type (CPT) 'Cooking Classes' but encounter redirection and 'Invalid post type' errors. Solution: We recommend the following steps to troubleshoot and resolve the issue: Ensure that the custom post type 'Tours' is properly configured for translation in WPML. Go to ACF > POST TYPES > TOURS > EDIT, select WPML translation Editor, and click the + sign to translate it. If these steps do not resolve the issue or if you encounter further problems, it might be due to outdated information or a different configuration. 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: The client wishes to remove the language selector from the admin login page that reappeared after installing WPML, despite previously using a code snippet in their theme-child functions.php to hide it. Solution: If you're experiencing the re-emergence of the language selector on the admin login page after installing WPML, we recommend navigating to WPML > Settings > Login and registration pages. Here, disable the option "Show Language Switcher on login and registration pages" to remove the language switcher.
This solution might be irrelevant if it's 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 for further assistance.
Issue: The client cannot find clear instructions on how to configure WPML in a multisite environment so that all hreflang links for subsites are included in the
of each subsite. Client wants hreflang links for parent pages and subpages to be automatically generated on US and UK sites.
Solution: First, we clarify that WPML can work individually on the main site or each subsite of a multisite network, but it cannot connect different sites within a multisite network. Each subsite has its own independent installation of WPML. Therefore, it is not possible to translate content from one subsite to another (for example, from Subsite 1 to Subsite 2).
To configure hreflang bindings, the client must manually add languages for all sites provided in each subsite. For example:
If this solution is not relevant For your case, because it is outdated or does not apply to your situation, we suggest opening a new support ticket. We also strongly recommend reviewing the known issues, checking the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, feel free to contact us at the WPML support forum.
Problem: The client wanted to restrict other administrators from using the Automatic Translation feature in WPML. Solution: We informed the client that it is possible to turn off other admins from using Automatic Translation in the Advanced Translation Editor (ATE), but they can still send content to automatic translation from WPML > Translation Management. This restriction applies to the Translation Manager as well. We recommended following the documentation:
However, we also clarified that there is no way to completely limit an administrator from using the automatic translation feature.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, we highly recommend checking related 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 with us.
Problema:
Después de clonar un sitio a otro dominio para una nueva sede en otro país, aparece un mensaje de WPML que indica un cambio en la URL del sitio y bloquea la pantalla de ajustes de WPML, impidiendo la edición de traducciones.
Solución:
WPML debe ser registrado cada vez que se cambia el servidor o se cambia el dominio o el proveedor del dominio.
2) Ahora ingreses la nueva URL del sitio. Esto crea una nueva clave de sitio.
4) Hagas clic en "Mostrar clave" y cópielo.
5) Ingreses la clave en Plugins > Añadir nuevo > Comercial (pestaña) para registrar WPML nuevamente. Si WPML todavía está registrado aquí, primero canceles su registro.
Si estás experimentando este problema después de registrar tu sitio nuevamente, te recomendamos que vayas a WPML > Soporte > Solución de problemas y utilices la opción para
"Forzar el funcionamiento del Editor de traducción avanzado en este sitio"
. Esto debería resolver el problema y permitirte editar las traducciones normalmente.
Si esta solución no parece relevante o si continúas teniendo problemas, por favor, abre un nuevo ticket de soporte en nuestro foro de soporte.
