Problem: The client needed to set a different logo for different languages in both the Header and Footer. Solution: We reviewed the theme documentation and identified the relevant text domain and option name for the logo settings. Here are the steps we followed: 1. Located the text domain
admin_texts_xts-woodmart-options
and the option name
[xts-woodmart-options]default_header
. 2. Navigated to WPML → String Translation. 3. Added the translation for the Serbian header from
header_866760
to
header_226231
. This change successfully updated the logos for different languages in the header and footer.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the related 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: You are experiencing an issue where the featured image set for a translated post disappears after some time, although it appears correctly in the original language. Solution: If you are setting the Featured Image for the translated post directly in the WordPress editor, this might not be necessary. When you translate a post, the featured image from the original post is automatically copied and synchronized with the translation. If you wish to use a different featured image for each language, we recommend following the steps described in this documentation.
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: If you're experiencing difficulties with translating the complete footer in your website, Solution: We recommend that you first navigate to WPML → String Translation and search for the strings that still need translation. If you do not find them there, you should check the Admin Texts Translation section. For detailed guidance, please visit https://wpml.org/forums/topic/split-set-a-different-logo/. If the issue persists, please inform us about how the footer was created (whether through a theme builder, Elementor, WPBakery, widgets, or a custom template). This information will help us determine where the strings are stored and how they should be translated.
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 still exists, we encourage you to open a new support ticket at WPML support forum for further assistance.
Problem: The client needs to switch the language setup from Bosnian ('bs') to Serbian ('sr'), including changing the flag and the language code on their website. Solution: We recommend the following steps to address this issue without needing to re-translate the content: 1. Add the Serbian language in WPML under 'Languages'. For detailed instructions, visit Editing WPML's Languages Table. 2. Duplicate the content from Bosnian to Serbian using the WPML 'Translation Dashboard'. For more information on how to do this, please see Duplicating Content.
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 WPML support forum.
Problem: The client was unable to translate products using Elementor after installing the WPML plugin. Certain text within the Product Template was not appearing in the WPML translation editor.
Solution: 1. We advised the client to set the Woodmart Layouts to "Translatable" in WPML > Setting > Post Type Translation > Layouts (woodmart_layout) and then proceed to translate them. 2. For the untranslated string in the footer bar, it should be translated using WPML > String Translation. If the string is not visible there, the client should follow the guide to find and register the string for translation: finding strings that don't appear on the string translation page, and ensure the correct source language is set: how to change the source language of strings. 3. We recommended changing the WPML settings from "Translatable - use translation if available or fallback to default language" to "Translatable only show translated items" for both products and templates to ensure proper functionality. 4. We installed an update for the WooCommerce Multilingual addon to address compatibility issues, detailed here: WooCommerce Multilingual 5.5.0.
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 problems persist, please open a new support ticket.
Problem: You are developing a site and trying to translate the Home page to English using WPML. Despite following the provided instructions, the Home page reverts from English back to its original language. Solution: We have recently released WPML version 4.7.6, which addresses this specific issue. We recommend taking a full backup of your site before proceeding. After ensuring your site is backed up, please update WPML to the latest version. Once the update is complete, verify if the Home page remains in English as expected.
If this solution does not resolve your issue or 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 the problem persist, please do not hesitate to open a new support ticket with us for further assistance.
