Problem: If you're experiencing a 404 error when trying to save a translated page and see an error in the JS console about the 'admin-ajax.php' file, it might not be directly related to WPML. Solution: We recommend the following steps: 1. Temporarily deactivate WPML and try updating the page in the default language. If the 404 error still occurs, it confirms that the issue is not related to WPML. 2. Deactivate other plugins one by one to identify if any are causing the issue. In this case, deactivating the Classic Editor plugin resolved the error. 3. If a specific page is causing the issue, try creating a new page and copying the content from the problematic page, then delete the original page.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Si esta solución no resuelve el problema o si la información proporcionada se ha vuelto obsoleta o no se aplica a tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable que revises los problemas conocidos en https://wpml.org/known-issues/, verifiques la versión del arreglo permanente y confirmes que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problema: El cliente tiene un sitio web en español y ha realizado traducciones al euskera. Tras modificar el contenido en español y tratar de traducirlo nuevamente al euskera, los contenidos iniciales aún aparecen en el traductor avanzado, impidiendo la creación de páginas en euskera. Solución: Si estás experimentando este problema, te recomendamos verificar si tienes tickets duplicados abiertos en nuestro sistema, ya que esto podría estar causando la repetición de contenidos en el traductor avanzado. En este caso, hemos marcado el ticket como resuelto para evitar duplicados en el foro.
Es posible que esta solución no sea relevante si ya no es aplicable o si no se ajusta a tu caso. Te recomendamos revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Si el problema persiste, por favor, abre un nuevo ticket de soporte en nuestro foro de soporte.
Problema: El cliente tiene un sitio web en español y ha realizado traducciones al euskera. Tras modificar contenido en español, los contenidos iniciales para traducir en el traductor avanzado no se actualizan y siguen apareciendo, impidiendo la creación de páginas en euskera. Solución: Este problema ya se había tratado en un ticket anterior. Para evitar duplicados, hemos marcado este ticket como resuelto. Si el problema persiste y los pasos anteriores no han resuelto la situación, recomendamos abrir un nuevo ticket de soporte. Además, sugerimos revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: The client was unable to preview or update posts in both the original French and the English translation after creating a translation using WPML. They encountered a 403 error, which persisted even after deactivating all plugins except for essential ones. The issue was linked to the 'aioseo' plugin triggering Apache's mod_security 'critical' alerts, which blocked the capability to save a post. Solution: We recommended deactivating all plugins except for the WPML ones to check if the issue persists. The client discovered that the 'aioseo' plugin was the cause of the 403 errors. Disabling or adjusting the settings of the 'aioseo' plugin should resolve the issue.
If this solution does not apply to your case, or if it 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 at our support forum.
Problem: You are receiving spam emails on email addresses linked to websites after using WPML. You suspect that WPML might be causing this issue. Solution: We suggest that the presence of your email address on the website's pages might be the reason for receiving spam emails, rather than the use of WPML itself. Since WPML only makes your site available in multiple languages, it does not influence the security of email addresses displayed on your site. To reduce spam, consider removing your email address from the website or replacing it with a contact form. This way, your email remains hidden from public view, reducing the likelihood of receiving spam. If you still suspect WPML is causing the issue, try disabling WPML temporarily to see if the spam emails stop. This can help determine whether WPML is related to the problem.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, do not hesitate to open a new support ticket with us for further assistance.
Problem: You have a multilingual website with 7 languages and want to use automatic translation for certain languages and manual translation for others, specifically for blog posts. However, the auto-translate feature tried to translate already translated posts and corrupted the Blog page. Solution: If you're experiencing this issue, we recommend you configure your WPML settings to selectively use automatic translation. Here's how you can do it: 1. Navigate to WPML -> Settings -> In the first section, set the configuration to automatically translate only the content you select. 2. Go to WPML -> Translation Management, select the blog posts you wish to automatically translate, and send them for automatic translation. Save the changes after each step.
Please note that 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.
Problem: The client is experiencing a PHP fatal error due to WPML_Gutenberg_Config_Option being defined twice in a WordPress environment using version 6.7.2 and sitepress-multilingual-cms.4.7.0. The error might stem from an incorrect update or usage by the previous developer. Solution: 1. We recommend manually removing the
sitepress-multilingual-cms
folder from the plugins directory and then re-uploading it after downloading the latest version from your WPML.org account. This action should resolve the issue of the class being defined twice. 2. Increase the WordPress memory limit to at least 128MB, as recommended by WPML. You can do this by adding the following line to your
Ensure to place this code above the line /* That's all, stop editing! Happy blogging. */. You can verify the updated memory limit in the WPML -> Support section of your WordPress dashboard.
If this solution does not apply to your case, or if it 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. Should issues persist, please open a new support ticket at WPML support forum for further assistance.
