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: 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.
