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.
Problem: The client was experiencing an issue where the 'Place order' button text in the checkout section of their website remained in English despite being translated into Serbian. Solution: We recommended updating the WPML and String Translation plugins to the latest version. After the update, the translation for the 'Place order' button should display correctly in Serbian.
If you're experiencing a similar issue, we recommend you try updating your WPML and String Translation plugins to the latest versions. If the problem persists, it might be due to an outdated solution or because it's not applicable to your case. In such instances, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket with us.
