Problem: The client is experiencing issues with incorrect URLs in the product sitemap for foreign languages, where untranslated slugs from the original language are being used instead of the translated ones. Solution: If you're facing similar issues with your sitemap URLs when using WPML and Rank Math, we recommend installing and enabling the WPML SEO bridge plugin. You can find detailed guidance on setting up and optimizing your multilingual website with Rank Math and WPML in our documentation: https://wpml.org/documentation/plugins-compatibility/optimize-multilingual-websites-using-rank-math-and-wpml/ and https://rankmath.com/kb/multilingual-seo-wpml/. After activating the plugin, you should regenerate the sitemap by going to Rank Math SEO -> Sitemap Settings. Make a minor adjustment to enable the 'Save Changes' button, click it, and then revert the change if necessary. This action should update the sitemap.
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.
Problem: The client is experiencing issues with the language options not appearing in the menu and footer on their website. Additionally, there is a failure in updating the preview on the setup page. The client has tried various browsers and updated WPML to the latest version, but the issues persist. Solution: We identified a conflict between WPML and LiteSpeed Cache, specifically with the Lazy Load Images feature. To resolve this: 1. Disable LiteSpeed Cache > Page Optimization > Media Settings > Lazy Load Images. 2. Alternatively, keep Lazy Load Images enabled but activate the option "Add Missing Sizes" to avoid the issue. 3. To address the margin issue between the flag and the text, apply the following CSS at WPML > Languages > Language switcher options > Additional CSS:
#menu-item-wpml-ls-70-en > a > img, #menu-item-wpml-ls-70-it > a > img {<br /> margin-right: 6px;<br />}
4. Exclude flags from the language switcher from the lazy load by: a. Navigating to LiteSpeedCache > Page Optimization > Media Excludes > Lazy Load Image Class Name Excludes b. Adding the class wpml-ls-flag and saving changes. c. Purging all caches from LiteSpeed Cache.
If these steps do not resolve your issue, or if the solution becomes 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 the problem persists, please open a new support ticket.
Problem: You are trying to translate images on your site using WPML, but some images are not being translated using media translation. This issue is related to a compatibility problem between the Real Homes theme, Easy Real Estate plugin, and WPML Media Translation. Solution: 1. Continue using WPML Media Translation to upload media for second languages. For Listings, apply the following workaround: - Go to WPML > Settings > Custom Field Translation and search for the field "REAL_HOMES_property_images". - Unlock the field and set its translation preference to "Don't translate". This allows you to manually select images on the translated post. 2. If displaying different images in different languages, upload alternative media files for the second languages at WPML > Media Translation. 3. If using the same image in both languages, check settings at WPML > Settings > Media Translation for options on duplicating media and making metadata from images available in the WPML Translation Editor. 4. Visit this link and then add the custom XML configuration to WPML > Settings > Custom XML Configuration to handle the translation of property images: https://wpml.org/forums/topic/some-images-are-not-being-translated-using-media-translation/?paged=2#post-17452664 After adding this, update the original property and then update its translation.
If this solution does not resolve your issue or seems outdated, 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. We highly recommend opening a new support ticket if needed.
Problema: El cliente está intentando realizar traducciones en su sitio web utilizando WPML con el constructor de páginas NHD Builder. Al traducir, las páginas en los nuevos idiomas presentan problemas de diseño: los estilos no se cargan correctamente y la disposición de los elementos se rompe. Solución: 1. Verificamos que el NHD Builder no está validado por nuestro equipo de compatibilidad. Puedes consultar otros constructores de páginas compatibles con WPML en esta lista. 2. Recomendamos contactar al servicio de soporte de NHD Builder para confirmar si sus productos son traducibles. 3. Como alternativa, puedes traducir manualmente el contenido utilizando el editor de WordPress, lo que debería permitirte mantener el uso del constructor. 4. Si deseas solicitar un reembolso, puedes hacerlo en esta página.
La solución podría no ser relevante si la información está desactualizada o no aplica a tu caso. Te recomendamos revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Si el problema persiste, te sugerimos abrir un nuevo ticket de soporte en nuestro foro de soporte.
Problem: If you're using the Uncode Theme and experiencing issues where your translated pages include buttons with internal links not pointing to the correct target language, this might be due to corrupted string packages. This problem was noted especially after editing and saving the original homepage. Solution: First, ensure that all your themes and plugins, including Uncode and WooCommerce, are updated to their latest versions. Then, follow these steps: 1. Navigate to WPML > Packages and delete the existing package for the homepage, which might be corrupted. 2. Edit and save the original homepage to allow WPML to create a new, hopefully uncorrupted, string package. 3. Reapply the translations for the homepage. 4. Repeat the process for any other affected products. If you continue to face issues, it might be helpful to switch the translation method to "WPML Translation Editor" from the WordPress Editor and reapply the translations manually.
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. Should problems persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
