Problem: The client reported that their website crashed and the German translation pages appeared strange. The hosting provider informed the client that the database was locked due to exceeding the available storage space, and recommended deleting unnecessary data to unlock it. Solution: We advised the client to contact their hosting service for more information about the issue, specifically asking whether any of WPML's database tables, prefixed with
wp_icl
, were causing the database to exceed its storage limits. We also suggested checking if they could log into their site to further diagnose the problem.
If this solution does not resolve your issue, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: El cliente enfrenta múltiples problemas con las traducciones en su sitio web: las traducciones no se reflejan correctamente en el front, el idioma secundario no muestra la bandera, y ciertos contenidos como el footer y partes de la home no aparecen traducibles o asignables en el idioma catalán. Solution: 1. Para los elementos no registrados como traducibles en Elementor, seguimos los pasos de nuestra guía para registrar elementos personalizados: https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/ 2. Las páginas que no aparecen en el menú en catalán estaban en la papelera. Es necesario restaurarlas y asegurarse de que estén publicadas. 3. Para el problema del footer y otros elementos no asignables, recomendamos contactar al soporte del tema para revisar el código y asegurar que las plantillas sean visibles en cada idioma. 4. Si se utilizó Elementor para traducir y no se reflejan los cambios, se debe editar la página en el idioma original haciendo pequeños cambios y luego guardar y actualizar la traducción.
Si esta solución no resuelve tu problema o parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/ y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más ayuda, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: The client is facing issues with translations not saving on their medical website. Solution: We recommend checking the issue by translating directly using the pencil link from the page editor. If the problem persists, please provide the translations so we can investigate further. Additionally, ensure that you have the latest versions of themes and plugins installed. 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that translations originally created with the Classic Translation Editor (CTE) were unexpectedly opening in the Advanced Translation Editor (ATE), despite the setting to use ATE for older translations being disabled. Solution: We investigated and found that the posts in question had been previously edited using ATE, which caused them to continue opening in ATE. We manually switched the editor for the specific post back to CTE. To prevent this issue, ensure the option 'Use also for old translations created with the Classic Translation Editor' remains unchecked in WPML → Settings. If you encounter similar issues or prefer to use CTE for other posts, please inform us, and we can apply the same adjustment.
Please note that this solution might not apply to your case if it's outdated or not relevant. 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: The client accidentally set their site to automatic translation, which depleted their translation credits significantly. After attempting to reset by disconnecting, removing, and reinstalling the plugin, the client found they only had a small fraction of their original credits left. Solution: Unfortunately, once translation credits are used, they cannot be restored as they are immediately compensated to the translation engine. More details can be found here: https://wpml.org/faq/can-i-get-a-refund-for-automatic-translation-credits/
If this solution does not apply to your case, or if it seems outdated, we 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 issues persist, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with translating content into English using WPML, where updating content in the primary language (Czech) and then switching to ATE results in the content for translation not loading and displaying the message: 'Unable to retrieve job details,' it might be due to the translation job containing no translatable data. This issue could be evident across multiple sites using the WPML plugin. Solution: We recommend checking the .xliff file generated by WPML. If the
<body>
element within the .xliff file is empty and the 'wpml-words-to-translate-count' is '0', it indicates that WPML is unable to extract any translatable content. This could be due to server-side issues rather than a problem with WPML configuration, plugins, or themes. Possible server-side causes include multiple applications of output compression (e.g., zlib.output_compression in PHP combined with server-level gzip/Brotli), modifications by security or performance layers (e.g., WAF, CDN, reverse proxy, or caching layer), or incorrect headers or content encoding (e.g., globally applied 'Content-Encoding: gzip'). To resolve this, contact your hosting provider, explain the issue, and ask them to investigate how responses are encoded and compressed on the server. This step is crucial especially if the issue affects multiple sites, suggesting a shared server configuration problem.
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 the problem persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that automatic translation does not translate all fields in Elementor widgets; some text fields remain untranslated despite being marked for translation in WPML settings. Solution: We recommended adjusting the translation preferences for custom fields and using the Multilingual Tools plugin to ensure WPML recognizes all text fields for translation. Here are the steps: 1. Install the Multilingual Tools Plugin from https://github.com/OnTheGoSystems/multilingual-tools. 2. Create a test page with the problematic widgets and fill in all text fields. 3. Generate XML configuration by updating the page and copying the XML code from the 'WPML: Elementor Widgets' section. 4. Add the custom XML configuration to WPML under 'WPML → Settings' in the Custom XML Configuration tab. 5. Resave the original page to force WPML to re-scan with the new configuration. 6. Re-translate the page using WPML's Translation Dashboard or Advanced Translation Editor.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that the Arabic version of their website was not displaying correctly after updating WPML plugins. Solution: 1. We advised the client to check and verify their WPML site registration key under Plugins → Add New Plugin → Commercial tab. 2. We suggested increasing the WordPress memory limit by adding the following code to the wp-config.php file:
3. We recommended deactivating the Slider Revolution plugin and any other related plugins to see if the issue resolves. 4. We created a staging site to further investigate the issue, where it was discovered that the problem was not with WPML but potentially with the Ave theme or incorrect HTML format.
If this solution does not resolve your issue, or if it 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.
