Problem: You are experiencing issues where the design elements such as background and font colors do not match between the original English page and its Norwegian translation after editing the original with Beaver Builder. Solution: We have addressed this issue in our latest updates of WPML. We recommend updating your WPML plugins to the latest version to ensure compatibility and correct synchronization of design elements across translations. If after updating, the problem persists or if this solution does not apply 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client created a translation of a 'my courses' page using the [ou-courses] shortcode to display courses the user is enrolled in. However, the translated page displayed a message indicating no enrolled courses were found, likely because it was trying to retrieve only translated courses. Solution: We recommended setting the post type 'Courses' to 'Translatable - use translation if available, or fallback to default language' in WPML > Settings > Post Type Translation. This configuration allows the display of the original course in the second language if they have not been translated. For more details, visit Displaying Untranslated Content on Pages in Secondary Languages.
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. If issues persist, please open a new support ticket.
Problem: The client was experiencing an issue where after logging in on the Norwegian version of their site using the Uncanny Toolkit's [uo_login_ui] shortcode, they were redirected to a 'Page Not Found' error instead of the intended page. Additionally, the user was not actually logged in. Solution: We identified that the issue was related to the language URL format used on the site. To resolve this, we recommended changing the URL format from directories to parameters. Specifically, this involved navigating to WPML → Languages → Language URL Format and switching from /no/ to ?lang=no. This change successfully resolved the login and redirect issues. For further details on similar issues, you may check the errata documentation here: WPML Errata Documentation.
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.
