The admin user named 'm***u' is unable to view the Translations queue in the WPML Translations menu, as it appears empty.
Solution:
First, verify if the translations are already assigned to another translator by navigating to WPML >> Translation Management >> Translation Jobs.
Next, ensure that 'm***u' is added as a Translator in WPML >> Translation Management >> Translators. For further guidance, refer to the WPML documentation on admin capabilities and working as a reviewer:
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Please 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, visit our support forum at WPML Support Forum.
Problem: You are encountering an issue where sidebar widgets disappear on .xml 404 pages within a language directory, while they appear as expected on regular 404 pages. This problem is observed in a setup using WPML with the WPML SEO plugin and a Genesis child theme. Solution: We have investigated and determined that this issue is likely not related to WPML directly. It appears to be associated with how templates are loaded for non-PHP files, such as XML. If you're experiencing this issue, we recommend checking your theme or server configuration to ensure that XML pages are handled correctly. Additionally, verify that your theme supports widget display on XML-generated 404 pages.
If this solution does not resolve your issue or seems irrelevant due to being 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 problems persist, please open a new support ticket.
Problem: The client reported that their website, which uses the ACF plugin, experiences freezing during the save process when WPML is active. The error message displayed is "Application did not respond in time." This issue does not occur when WPML is deactivated. Solution: We investigated the issue by testing without WPML, ACFML, and with a default theme. The problem persisted, indicating it is not solely related to WPML. We observed that the issue might be related to server resource limitations such as PHP memory limit or server response time. We recommend: 1. Checking the PHP error logs for detailed information on failures. 2. Consulting with hosting support to possibly increase server resources. 3. Considering an update to the PHP version. For issues related to slow performance or increased queries, we suggest consulting this carefully curated list of items. If the problem persists after improving server resources, and you suspect WPML might still be impacting performance, please let us know.
Please note that this solution might be 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, we encourage you to open a new support ticket at WPML support forum.
Problem: The client is facing an issue where the automatic currency conversion rate update is not working as expected on their website. They are concerned about potential conflicts due to having over 40 plugins installed. Solution: We recommend the following steps to troubleshoot and resolve the issue: 1) Ensure that WooCommerce and WCML are updated to the latest versions. Before making any changes, take a full backup of your website and database. 2) Deactivate all plugins except for WPML, String Translation, WCML, and WooCommerce. 3) Switch to a standard theme, such as Twenty Twenty-Four or Twenty Twenty-One. 4) Check if the issue still occurs. 5) Reactivate the plugins one by one, checking for the issue after each activation to identify any conflicts. 6) If the issue does not reappear after all plugins are activated, switch back to your original theme to check if it is the cause. Additionally, consider that cron jobs require time to run, typically scheduled every 24 hours. You can use cron manager plugins from WordPress.org to manage and test cron jobs. For further debugging, enable WPML's debugging feature as described at https://wpml.org/documentation/support/debugging-wpml/ and monitor the /wp-content/debug.log file for any errors during the cron job execution.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, please visit our support forum at https://wpml.org/forums/ to open a new support ticket. We also 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.
Problem: If you're experiencing repeated '/en/' in your URL while using WPML, it might not be an issue with WPML itself. This problem could be due to server-side errors that occur when headers are sent before the output, especially when the URL includes a language code like '/en' or '/fr'.
Solution: We recommend checking your server for any errors that might be outputting before headers. This issue occurs in both the frontend and backend, regardless of whether debugging is on or off.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at 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: The client reported issues with translations not showing correctly after renaming a custom post type from 'Products' to 'Places'. Specifically, the English versions of the pages were not appearing, and tags were displayed in both English and Arabic instead of only English. Solution: Renaming custom post types with existing content can lead to unexpected behavior, including issues with translation associations and language metadata. To address potential database inconsistencies caused by the renaming:
Check
wp_posts.post_type
to ensure all translated entries are still listed as 'product'.
Verify
wp_postmeta.meta_key
for keys like _wpml_word_count and _wpml_media_duplicate to confirm they're intact.
Ensure
icl_translations.element_type
is set to 'post_product' for all translations.
Confirm the correct language assignment in
icl_translations.language_code
.
Make sure translated posts share the same Translation ID (trid) as the originals in
icl_translations.trid
.
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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: The client updated translations using the WPML editor, and while the page displayed the updated content, WPML still showed an old version of the text. The client was unable to make further edits due to WPML not reflecting the changes. Solution: The issue was resolved by the client themselves. It was discovered that there were two conflicting versions of the article. Once the client restored one autosave, it resolved the conflict and allowed WPML to reflect the updated translations correctly. If you're experiencing similar issues, we recommend checking for any conflicting versions or autosaves that might be causing the problem.
Please note that this solution might be 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: Du erlebst, dass sich das Seitenlayout je nach Sprache unerwartet ändert, wobei das Template von 'Elementor Full Width' zu 'Default Template' wechselt. Dies geschieht sowohl bei neuen als auch bei bestehenden Seiten. Solution: Da das Problem auch ohne WPML auftritt, liegt es nicht an WPML. Hier sind die Schritte, die Du unternehmen solltest: 1) Erstelle eine Staging-Kopie Deiner Website. 2) Deaktiviere alle zusätzlichen Plugins außer WooCommerce. 3) Wenn das Problem verschwindet, aktiviere die Plugins einzeln oder in kleinen Gruppen wieder, um den Verursacher zu identifizieren. 4) Sollte das Problem weiterhin bestehen, wechsle zu einem Standardthema wie Twenty Twenty-One, um zu prüfen, ob das Problem am Thema liegt. 5) Kontaktiere das Support-Team des betreffenden Plugins oder Themas, falls das Problem weiterhin besteht.
Falls diese Lösung veraltet ist oder nicht auf Dein Problem zutrifft, empfehlen wir, einen neuen Support-Ticket zu öffnen. Wir empfehlen auch, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Du die neuesten Versionen von Themes und Plugins installiert hast. Für weitere Unterstützung besuche bitte unser Support-Forum.
Problem: You are trying to change the default text in the 'woocommerce-multilangual' plugin for WPML because the current notification text is unclear, causing users to mistakenly click the wrong button and empty their cart. Solution: We recommend using the WPML String Translation to 'translate' the original language text to the desired text, effectively changing it. This method involves treating the original text as if it were a foreign language and providing the desired text as the 'translation.' Alternatively, you can use the Loco Translate plugin, which allows editing of strings in the original language. However, please note that directly editing plugin files is not recommended as updates to the plugin will overwrite these changes.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket.
Problem: You are experiencing missing translations on local pages after making changes in the default language, and you are also facing issues with opening WPML and the WPML Translation Editor. Solution: To determine if a page’s content was initially created using the Classic Translation Editor or the Advanced Translation Editor, first check if the content appears in the Advanced Translation Editor. If it does, the translations were done using the Advanced Translation Editor. If the frontend shows content but the Advanced Translation Editor is empty, check the Classic Translation Editor. If the content appears there, it means the page was translated using the Classic Translation Editor. If the frontend shows content but both the Advanced Translation Editor and the Classic Translation Editor are empty, then further troubleshooting is necessary as this situation is usually not possible.
Please note that this solution might be 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 at WPML support forum for further assistance.
Problema: Estás intentando traducir páginas en WPML, pero en lugar de abrir el editor de traducciones, parece como si estuvieras creando una página nueva o se abre la traducción de otra página. Esto podría indicar un conflicto con la plantilla del tema. Solución: Si estás experimentando este problema, te recomendamos seguir estos pasos: 1. Edita una de las páginas en el idioma original. 2. Ve a la columna derecha y busca el bloque 'Idioma'. 3. Haz clic en el botón 'Editor de Traducción'. 4. En la ventana emergente, selecciona que los cambios apliquen para todo el contenido del sitio. 5. Guarda los cambios. 6. Comprueba si el problema se resolvió.
Si la solución proporcionada no resuelve tu problema o parece ser irrelevante 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 relacionados, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Si necesitas más asistencia, no dudes en contactarnos en nuestro foro de soporte.
