Problem: You are experiencing issues where English strings are still appearing on the French version of your page, despite having translated them. Solution: We have reviewed your translations and confirmed that you have correctly used the Advanced Translation Editor for translating the strings. It appears that the translations are displaying correctly on the frontend of your site. If you're still seeing English strings, we recommend clearing your site's cache and ensuring that all translations are published and not in draft status. Additionally, double-check that the language settings are correctly configured to display the French translations for your audience.
If this solution does not resolve your issue or seems outdated, please visit our known issues page to check for any related problems. Ensure you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: You are trying to change the main font family to 'TAJAWAL' for Arabic text only on your website, but the default theme font is being applied instead. Solution: To apply the 'TAJAWAL' font to Arabic text only, you can use custom CSS. Here is an example of how you can specify the font for Arabic content:
This CSS rule targets the body element only when the content language is Arabic (specified by :lang(ar)) and applies the 'TAJAWAL' font. Ensure you add this CSS to your theme or via a custom CSS plugin.
If this solution does not resolve your issue or 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problema: Estás intentando eliminar un mensaje del editor en tu sitio web, pero cada vez que lo guardas, vuelve a aparecer. Solución: Este comportamiento ocurre porque has traducido el contenido utilizando el Editor de Traducción de WPML. Para actualizar la traducción y evitar que el mensaje vuelva a aparecer, debes usar el mismo Editor de Traducción. Si prefieres desactivar esta función, puedes seguir los pasos descritos en la siguiente guía: Usando diferentes editores de traducción para diferentes páginas.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
Problema: El cliente estaba tratando de resolver un problema de redirecciones en su sitio web y tenía un ticket abierto que desapareció del listado de soporte de WPML. Solución: Si estás experimentando este problema, te recomendamos verificar tu perfil de usuario en la sección de 'Temas del foro creados' para encontrar tickets que no aparecen en el listado principal. Si el problema persiste o la solución proporcionada aquí es irrelevante debido a que podría estar desactualizada o no aplicarse a tu caso, te sugerimos abrir un nuevo ticket de soporte. Además, te recomendamos encarecidamente revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: The client is experiencing automatic 301 redirects on all translated pages of their multilingual website, redirecting each non-English page to its English counterpart despite the 'Redirect visitors based on browser language' option being disabled in WPML settings. Additionally, translated pages are automatically assigned a slug ending with -2, even though no duplicates exist. Solution: For the issue of 301 redirects, it appears that the redirects are expected behavior when accessing the default language page directly. The Italian version of the page should be accessed via its correct path, which includes the language directory, e.g.,
https://caalvise.com/it/contatti/
. This should resolve the indexing issues as the correct URLs will be accessed. Regarding the slug issue with '-2', it was identified that there is indeed a page with the original slug 'hotelsinvenice' on the site. The client can edit this page directly by accessing https://caalvise.com/wp-admin/post.php?post=87801&action=edit&lang=en.
If these solutions do not resolve your issues or seem irrelevant due to being outdated or not applicable to your case, we recommend opening 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is finishing translating their website using WPML and wants to know how to implement tracking codes such as Google Analytics, Google Search, Tag Manager, IndexNow, and Yandex across different domains. Solution: We explained that WPML does not directly handle the implementation of tracking codes like Google Analytics, Tag Manager, or Search Console. These codes should be inserted into the website's code, independent of WPML or translations. WPML only translates page content (text, images, etc.) and does not process, modify, or translate tracking codes. These should be managed directly in the site's theme, header, or through compatible WordPress plugins for script insertion. We recommend implementing the codes and checking if they are present across all the site's domains.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.
