Problem: The client was unable to transfer styles to translated pages, posts, and events using WPML, resulting in different styles appearing on the translated versions compared to the original. Solution: We advised the client to ensure that styles saved in custom fields are correctly copied to secondary languages. This involves adjusting the WPML settings for custom fields translation. Here are the steps we recommended: 1. Follow the guide on translating custom fields (https://wpml.org/documentation/getting-started-guide/translating-custom-fields/). 2. Navigate to WPML -> Settings -> Custom fields translation. 3. Check the 'Show "Multilingual Content Setup" meta box on post edit screen' option and save the changes. 4. When editing a post/page in the original language, adjust the configuration for the custom fields at the bottom of the page. 5. Set selectable or checkable custom fields to 'Copy' and text input fields to 'Translate'. 6. Update the translated page to reflect these changes.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend checking related known issues (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 for further assistance at WPML support forum.
Problem: You are trying to translate cart strings on your website, but the translated strings are not showing correctly in the cart. Instead of the expected translations, the default language strings are displayed. Solution: First, verify if your issue matches the known problem described here: WooCommerce Multilingual cart page strings not translated when using blocks. If it does, please follow the workaround provided in the link. We strongly recommend backing up your database before making any changes.
If this solution does not apply to your case, or if it seems outdated, we encourage you to open a new support ticket. We also 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.
Problem: You are trying to see a translated string in the WooCommerce Wallet system, but it is not displaying as translated. You expect to see 'Kredit u novčaniku kroz kupovinu #' but instead, you see 'Wallet credit through purchase #'. Solution: First, ensure you back up your site and database. Then, navigate to Plugins > Add new > Commercial and check for WPML updates. Install and activate the latest versions of our plugins. If updates are available for the WpResidence Theme or other plugins, please update them as well. After updating, reapply the translation for the string and check if the issue is resolved.
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 the problem persists, please open a new support ticket.
Problem: The client was experiencing issues with translated pages, posts, and portfolios losing styles and not displaying like the original. Additionally, some content was not appearing in the translation editor, and there were problems with untranslated strings in Elementor widgets and custom fields. Solution: 1. We registered the necessary Elementor widgets for translation by adding custom XML configuration in WPML->Settings->Custom XML tab. Here is the code used:
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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.
Problem: When attempting to register a new user, only the 'Agent' role was visible, while 'Agency', 'Developer', and 'User' were missing. This issue was due to a problem with string translation affecting user roles visibility when WPML was active. Solution: We collaborated with the WPResidence team to address this issue. Our compatibility team identified the problem and communicated a permanent solution to the WPResidence team. Meanwhile, we implemented a temporary workaround on your site. Please review the changes to confirm if the user roles are now displaying correctly. For more details, you can check the errata page here: WPML Errata.
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 see translated strings on the WooCommerce checkout and cart pages, and also had issues with missing roles in a registration form. Solution: For the checkout page, we set the legacy checkout as the official page using the shortcode
[woocommerce_checkout]
in WooCommerce > Settings > Advanced. This is a temporary workaround until a permanent solution is found.
For the cart page, we recommended using the WordPress editor to replace the new WooCommerce Cart blocks with a shortcode block containing
[woocommerce_cart]
, which displays the default cart page without translation issues.
Regarding the missing roles, this issue was similar to another reported problem. We suggested confirming if using the same naming from the English version displays the roles correctly. Additionally, we split this issue into a separate ticket for better handling and escalated it to the compatibility team.
If this solution does not resolve your issue, or if it 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to locate specific strings for translation within their WordPress site. They had tried searching through various categories and using exact matches but were unsure of the source of these strings, whether from a theme or a plugin. One string was in English, and another was automatically translated to Serbian with incorrect pluralization upon switching the WordPress language setting.
Solution: We recommended two methods to locate and translate the strings: 1. Navigate to WPML > String Translation and enable the option "Look for strings while pages are rendered" at the bottom of the page. Then, visit the front end where the string appears, return to WPML > String Translation, and search for the string. 2. If the string is not found in the WPML > String Translation, it might be categorized as an admin text string. For detailed steps on how to find and translate admin text strings, visit this documentation.
If these methods 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. If further assistance is needed, please open a new support ticket at WPML support forum.
