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.
Problem: The client is experiencing an issue where the hover color on multilingual buttons does not work on English pages of their WordPress site, despite working correctly on the main French page. The hover color is not applied even though it is correctly set up.
Solution: 1. We suggested clearing the Elementor cache by navigating to 'Elementor > Tools' and clicking on 'Clear data and Files Cache'. 2. We noticed that a CSS rule with the !important attribute might be overriding the hover color on English pages. We recommended using a less specific CSS rule or adjusting the existing one. 3. We advised checking the global style settings in Elementor for both languages and ensuring they are consistent. 4. We suggested making a minor modification to the content, such as adding a blank space, and then saving the changes to refresh the styles. 5. If these steps do not resolve the issue, we recommended opening a new support ticket for further assistance.
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.
Problema: En la versión móvil, el desplegable de idiomas se oculta casi completamente hacia la izquierda, impidiendo que el cliente pueda cambiar de idioma fácilmente. Solución: El problema identificado no es causado por los plugins de WPML, sino por el tema utilizado en el sitio. Recomendamos contactar con los autores del tema para una solución permanente. Como solución temporal, puedes añadir el siguiente CSS en WPML -> Idiomas -> CSS adicional para ajustar la visibilidad del desplegable:
@media (max-width: 1700px) {<br /> @sm-17549850343107527-2{<br /> margin-left: auto !important;<br /> margin-top: auto !important;<br /> }<br />}
Si esta solución no resuelve el problema o si el problema persiste, te recomendamos revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins. Si el problema sigue sin resolverse, no dudes en abrir un nuevo ticket de soporte.
The client is unable to see job postings when selecting the German language switcher on their website, which has English as the default language. They want job postings to be visible only in German and do not plan to translate the Career details page.
Solution:
We recommend creating the job posts only in German and setting up a redirection from the English job posts page to the German job posts page. Here are the steps to create job posts in German:
- Go to Job Manager >> Job Listings. - Use the dashboard language switcher in the top header to switch to German. - Create the job posts in German.
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 you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem: If you're experiencing issues when switching your site's language from German to English, particularly on the homepage, and encountering a timeout error, the problem might be related to your theme settings. Additionally, if your header and footer translations are sometimes not working, this could also be linked to the same issue. Solution: We found that the issue occurs only when both the Child Theme and Elementor Pro are active. Switching to the parent theme resolves the issue, indicating a problematic function in your Child Theme's code. We recommend commenting out the following code in your Child Theme:
function custom_shop_footer_output() {<br /> if (!function_exists('elementor_theme_do_location') || !elementor_theme_do_location('footer')) {<br /> get_footer('shop');<br /> }<br />}<br />add_action('wp_footer', 'custom_shop_footer_output');
This function likely causes an endless recursion leading to a timeout because it repeatedly calls itself. We suggest that you or your developer revise this function to prevent further errors.
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 issues persist, please open a new support ticket.
