Problema: El cliente tiene un problema donde la URL en inglés
https://www.vibraspeakeasy.es/en/menu/
ha dejado de estar vinculada a su versión original en español
https://www.vibraspeakeasy.es/carta/
. A pesar de que en el backend de WPML aparece como conectada, la conexión real entre las páginas no funciona correctamente. Solución: Para resolver este problema, hemos realizado los siguientes pasos: 1. Verificar manualmente las relaciones de traducción de WPML entre
/carta/
(ES) y
/menu/
(EN) a través del dashboard de traducción de WPML y el editor de páginas. 2. Revisar la configuración de Permalinks, la configuración de URL de idiomas de WPML, y si los slugs están configurados correctamente y las traducciones están asignadas como originales y traducciones. 3. Confirmar que la traducción de 'carta' está explícitamente configurada a 'menu' en inglés y revisar las asociaciones de post/página. 4. Modificar el slug de la página en inglés de 'menu' a 'menu-en' para resolver el conflicto causado por la presencia del mismo slug en otra parte del sitio.
Si esta solución no resuelve tu problema o si parece no ser relevante debido a que está desactualizada o no se aplica a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, no dudes en contactarnos en el foro de soporte de WPML.
Problem: The client is experiencing 404 errors on some translated pages, even after resetting permalinks. Solution: If you're encountering 404 errors on your translated pages, we recommend the following steps: 1. Ensure that the WooCommerce Multilingual & Multicurrency (WCML) plugin is active. 2. Check your WPML and WooCommerce settings for permalink and slug translations. 3. Review and correct the translated product slugs in WCML. 4. Reset your permalinks multiple times if necessary.
If these steps do not resolve the issue, it might be due to a configuration that is either outdated or not applicable to your specific 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that WPML incorrectly detected the REST API as disabled, despite WordPress and various tests indicating that the REST API was functioning correctly. Solution: We recommended creating a staging site to safely test solutions without affecting the live site. After initial tests did not resolve the issue, we escalated the ticket to our second-tier support. The solution involved applying a custom WAF rule in Cloudflare to whitelist the endpoint
/wp-json/wpml/v1/rest/status
. The rule needed to include specific conditions to ensure proper handling of requests. After applying the rule, the REST API was correctly recognized by WPML.
If this solution does not resolve your issue, or if it seems outdated, we recommend checking the 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 problem persists, please open a new support ticket.
Problem: The client needed help with disabling automatic translation in WPML. The automatic translation icon kept spinning, and the client was unable to find the option to turn off automatic translation. Additionally, there was confusion about the renamed menu items and a large post_meta table. Solution: To disable automatic translation, we recommended the following steps: 1) Ensure that the option "Translate Everything automatically" is turned off in WPML > Translation Dashboard. 2) In the Advanced Translation Editor, access the settings in the top right corner and disable "Translate all content automatically when the editor is opened". 3) In WPML > Translation Tools > Automatic translation engines, disable all automatic translation engines. 4) In WPML > Translation Tools > Who can use Automatic Translation?, ensure that no admin or translator is enabled for automatic translation. Additionally, if the features of the Advanced Translation Editor are not needed, the client can switch to the Classic Translation Editor, which does not support automatic translation features like Glossary, Translation Memory, and Spellchecker. More information on using the Classic Translation Editor can be found here: Using the Classic Translation Editor.
If this solution does not resolve the 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where your translated page in Spanish shows incomplete content despite being fully translated in the WPML Translation Editor, and the translation job remains 'In Progress', this might be similar to a recent case we handled. The client had a Service page (Warehousing & Storage) that displayed full content in English but only a portion in Spanish. The issue persisted even though the WPML Translation Editor showed 100% completion, and it started after an update to the CMSMasters Elementor Addon.
Solution: We recommend checking if the section causing the issue is correctly added and translated. In the recent case, we resolved the problem by re-adding the problematic section and translating it again to Spanish. This approach successfully finalized the translation job and displayed the full content on the frontend Spanish page.
Please note that this solution might be irrelevant if it's outdated or not applicable to your specific 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.
