Problema: Si estás experimentando un error durante el paso 4 del asistente de configuración de WPML, donde aparece un loading pero luego no se carga nada y no puedes completar la configuración, este resumen podría ayudarte. Solución: Primero, asegúrate de tener una copia de seguridad completa del sitio. Luego, necesitaremos instalar temporalmente un plugin de administración de base de datos para hacer un pequeño ajuste en un elemento de WPML en la base de datos. Una vez confirmado que todo está preparado y la copia de seguridad está en su lugar, procederemos con el ajuste. Después de realizar estos pasos, verifica si el asistente de configuración completa sin errores.
Si esta solución no resuelve tu problema o 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 confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: You translated a page from English to French, but the content appeared in Spanish. Solution: We identified a minor issue on our server that caused this problem. We have since resolved the issue on our server. We recommend you select
Overwrite existing translations
and resend the post for automatic translation. If the problem persists, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If this solution does not resolve your issue or seems outdated, we encourage you to open a new support ticket. For further assistance, you can also visit our support forum.
Problem: If you're experiencing issues with ATE where it opens but gets stuck loading, and eventually displays an 'Execution Expired' error, this might be due to specific translation units containing large sections of encoded data. This problem was identified when the ATE failed to load the homepage, despite other pages working correctly. Solution: We recommend checking any content-heavy sections on your page for encoded data. For instance, if you have custom CSS in blocks like sliders where images are embedded directly as encoded (base64) data, update this to use a standard image URL from your Media Library. This change should reduce the size of the translation unit, allowing the page to be sent to ATE without issues. After making these adjustments, please attempt to send the page to translation again.
If this solution does not resolve your issue or seems outdated, 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 problems persist, please open a new support ticket.
Problem: WPML was unable to copy your site's translations, translation memory, and glossary to this new URL. Solution: If you're experiencing this issue, we recommend you watch this instructional video: https://kommodo.ai/recordings/SxSjoC14ovHvoQ286diP. Next, please follow these steps: 1. Ensure you are logged into wpml.org. 2. Navigate to
WordPress Dashboard > Plugins > Add New > Commercial (Tab)
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.
Problem: After accidentally deleting the custom DB prefix table 4b5SG_icl_translate, the client recreated the table with the standard WPML structure, executed TRUNCATE on icl_translate and icl_translate_job (141 broken jobs), reset the statuses from 1/2 to 0 in icl_translation_status (44 entries), and ran "Synchronize local task IDs with ATE tasks" multiple times. However, ATE works well on new pages, but on about 42 existing pages, the ⟳ "Update Translation" icon opens the native Elementor editor instead of ATE. The client suspects that the ATE source/target pairs for these pages are lost and needs to force a re-ingestion on the ATE servers. Solution: We suggested checking if the right editor is selected when modifying the page. This can be verified by looking at the right panel and the editor selected at the top, as shown in the screenshots provided. It's possible that the editor was set to "WP editor" instead of ATE. Additionally, we asked to check the URL displayed at the bottom of the page when hovering over the ⟳ icon to ensure it directs to ATE.
If this solution does not resolve the issue or seems outdated, or if it does not apply to your case, we highly recommend opening a new support ticket. Please also 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. For further assistance, you can contact us directly at the WPML support forum.
Problem: The client updated the privacy policy and homepage translations using the Advanced Translation Editor. Although the changes appear correct in the editor, they are not visible on the website's frontend. This issue is common with sites using page builders like Elementor and caching mechanisms.
Solution: 1. Clear WPML's internal cache and any site-level caches: * Go to WPML → Support → Troubleshooting in your WordPress admin. * Scroll down and use the options to clear caches. 2. If the issue persists, consider deactivating caching or optimization plugins temporarily to check if they are causing the issue. 3. If translations still do not appear, it might be necessary to check for server-level or host-managed caching outside of WordPress plugins and investigate possible synchronization issues between Elementor, the Astra theme, and WPML.
If these steps do not resolve the 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 problems persist, please open a new support ticket.
