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.
Problem: The client has a custom post type with translated slugs, but occasionally the archive page URL for the English site shows the Dutch slug instead of the English one. This issue is temporarily resolved by resetting the permalinks, but it can recur.
Solution: The problem occurs because, when registering the custom post types, the client uses a gettext call to define the post type slug. We recommend removing the gettext call from the rewrite slug in the custom post type registration and using a static text instead. Here's how to adjust the code:
After making this change, go to WPML > Settings > Post Types Translation to set the slug translations for your custom post type. If you prefer, you can also translate the slug using the String Translation feature, searching for the slug under the WordPress text domain.
