Problem: The client updated their checkout field and plugin to WP page builder and encountered an issue with translating a specific text field from the MailPoet plugin, which is not appearing on the WPML string translation page. The text field in question is for receiving exclusive emails with discounts and product information. Solution: We identified that the text is sourced from the MailPoet plugin, which is currently not compatible with WPML. To address this, we recommend the following steps: 1. Ensure you back up your site. 2. Attempt the solution provided in this WPML forum thread: https://wpml.org/forums/topic/translate-mailpoet-to-enable-customers-sentence/#post-7448773 3. If the problem persists, consider the suggestions in another WPML forum thread: https://wpml.org/forums/topic/i-would-like-to-receive-exclusive-emails-with-discounts-and-product-information/#post-16002068 If these steps do not resolve your issue, or if the solution becomes 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 open a new support ticket at WPML support forum.
Problem: The client is unable to translate the main language (English) strings on their multilingual site, despite being able to translate other languages. They are specifically struggling with translating payment option texts in the WooCommerce settings and cart. Solution: If you're experiencing issues with translating the main language strings on your site, we recommend the following steps: 1. Identify the strings you wish to translate and check the corresponding checkboxes on the left. 2. Scroll down to find a button that allows you to change the string's default language. Select a language that you have not set up on your site, such as "Romanian" or "Bulgarian". 3. After the page refreshes, you will see a new + icon on the right side under a new table column with the English flag at the top. Click the + icon, enter the desired English wording, and save your changes.
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: You have installed WC Page Builder to edit the shop page and imported the shop templates, but they are not translated and are only available in English. You are unable to find how to translate WC Page Builder strings and pages. Solution: 1) Go to WPML -> Settings -> Post Type Translation section, set the templates post type to be translatable, and then translate the templates. 2) We recommend that you share your Debug information with us to better understand your site configuration. You can find a detailed explanation on how to provide this information here.
If this solution does not apply to your case, or if it seems outdated, please check the 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 you need further assistance. You can do so at WPML support forum.
Problem: The client reported that the 'create an account with styleduo' field on the checkout page is not translated when not logged in, despite other elements being correctly translated. Solution: We recommended the following steps to resolve the issue: 1. Navigate to WPML-> String Translation. 2. If the string is not immediately visible, proceed to 'Translate texts in admin screens' by scrolling down and clicking on the link. 3. Search for the required strings. 4. Select the strings and click on the 'Add to String Translation' button. 5. Return to the String Translation page by clicking on the '« Return to String Translation' link. 6. Translate the strings, clear the cache, and then verify the changes on the front end. For more detailed guidance, please refer to our documentation on translating texts in admin screens: Translating texts that don't appear on the String Translation page.
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 has translated their header and footer using WPML, but the footer is only displaying in English across different language versions of the site. Solution: We found that the footer needs to be manually selected in the "Page Settings" section for each translated page. To resolve this issue, edit each translated page and ensure that the translated footer is selected. This adjustment was made on the homepage as an example.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
The client is unable to translate the footer of their website using WPML, despite having successfully translated the header. They are using the 7Up Theme.
Solution:
If you're experiencing this issue, we recommend checking if the Footer post type is set to be translatable. You can do this by navigating to WPML>>Settings>>Post Type Translation. Ensure you perform a site backup first, then set the option for the Footer post type to Translatable – only show translated items and save the changes. Afterwards, attempt to translate the Footer posts to see if the issue is resolved.
For more detailed guidance, please refer to our documentation on translating custom posts: Translating Custom Posts.
If this solution does not apply because it might be outdated or not suitable for 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is unable to activate the OTGS Installer for the WPML plugin on their new server, despite it working on a previous site. They are also unsure if they need to install the String Translation plugin along with the WPML Multilingual CMS for full functionality. Solution: If you're experiencing issues with activating the OTGS Installer, we recommend downloading the plugins manually. You can do this by visiting https://wpml.org/account/downloads/ and clicking on "Download WPML manually" at the bottom of the page. Regarding your query about the String Translation plugin, yes, you need to install it to translate strings from themes and plugins or to handle page builder content.
Please note that this solution might be irrelevant if it's outdated or not applicable 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. If the issue persists, please open a new support ticket at WPML support forum.
