Problem: After migrating the domain from gstcouncil.org to gstc.org and re-registering WPML with a new license key, some translation pages are not visible to users who are not logged in, showing a 404 error instead. The error log indicates a URL change detected by WPML. Solution: The issue was identified as related to the Toolset Access Plugin. We recommend checking the configuration of the Toolset Access Plugin to ensure it is not misconfigured, which might be restricting access to certain pages. If deactivating the Toolset plugin resolves the issue, confirming that pages become visible, further assistance should be sought from the Toolset support team. You can open a new ticket for Toolset-related issues at Toolset Professional Support.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at WPML 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 contact our support team for further assistance.
Problema: Estás intentando traducir automáticamente usando WPML, pero el recuento de palabras no es correcto. Estás trabajando con la plantilla AVADA y un child theme. El recuento de palabras en el backoffice muestra 5715, pero la página realmente tiene unas 232 palabras. Solución: El recuento de palabras que ves es un estimado y es normal que sea incorrecto en sitios que usan un page builder como Avada o Elementor y campos personalizados. Este conteo no afectará la cantidad de palabras que se envían a traducir. La cantidad de palabras que se envían a traducir será más cercana al número real de palabras en la página o igual a este. Además, este estimado no tiene en cuenta la memoria de traducción, que permite utilizar traducciones ya realizadas y por lo tanto no se te cobra en el momento de traducir el contenido. Puedes leer más sobre cómo WPML lleva un registro de tus traducciones en este enlace.
Si esta solución no resuelve tu problema o si la información parece desactualizada o irrelevante para tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos verificar los problemas conocidos en este enlace, confirmar que tienes instaladas las últimas versiones de los temas y plugins, y si necesitas más ayuda, visita nuestro foro de soporte en este enlace.
The client is facing an issue where slugs for French, Spanish, and Portuguese pages are being translated instead of being copied from the original English slug, despite enabling the 'Copy from original language if translation language uses encoded URLs' setting in WPML. This setting worked for Arabic but not for other languages.
Solution:
We recommend trying the following steps after ensuring you have a full site backup:
1) Navigate to WPML >> Languages >> Site Languages. 2) Click on the Edit Languages link. 3) In the table that appears, locate the "Encode URLs" column. 4) Set "Encode URLs" to "Yes" for all secondary languages, but leave the main language unchanged. 5) Click Save and clear all types of caches. 6) Test the setting by translating a new page to see if the slugs are copied correctly.
If this solution does not resolve your issue or 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.
