Problem: You are trying to hide the available language translations for pages but not for posts on your website. The current CSS solution only works for individual pages, not globally. Solution: We recommend applying the following global CSS to hide the language translations on all pages but keep them visible on posts:
After applying this CSS, please clear all sorts of site/server/CDN cache to see if this resolves the issue.
If this solution does not apply to your case, or if it 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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is trying to use WPML's AI translation feature but finds the available language options limited. Additionally, they are experiencing an issue with an unwanted globe icon appearing next to the menu language switcher in the Buddyboss platform. Solution: For the AI translation feature, WPML AI is currently available in a limited number of languages, and more are being added over time. Clients can check the list of available languages here. If the current languages do not meet the client's needs, it is recommended to use other translation engines like DeepL. Instructions for changing translation engines can be found here. For the issue with the Buddyboss platform, the client should try the workaround provided in the WPML errata here. If that does not resolve the issue, a CSS solution is available here.
If these solutions do not resolve your issues or if they seem outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues here, 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 here.
Problem: The client experienced issues with the WPML plugin causing conflicts on a platform using BuddyBoss. When WPML was activated, groups on the listing page were not accessible. Solution: We clarified that BuddyBoss Groups are not translatable by default; only the group title and description can be translated using WPML String Translation. Upon testing with the latest BuddyBoss Platform update, it appears that updating BuddyBoss resolves the issue. If you're experiencing similar issues, we recommend updating your BuddyBoss Platform and checking if the problem persists. Additionally, ensure that you are using the latest version of WPML and other plugins. For further assistance, please visit our support forum. We also 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 continues, please open a new support ticket.
Problem: The client is unable to activate the WPML String Translation plugin, even after updating all plugins, the theme, and WordPress itself. The issue persists with WPML 4.6.15 and String Translation 3.3.1. Solution: We recommend deactivating all plugins and then reactivating them one by one to identify any conflicts. In this case, the issue occurred with the BuddyBoss Integration and BuddyBoss Platform plugins. Here are the steps to resolve the issue: 1. Take a backup of your site. 2. Deactivate the BuddyBoss Integration and BuddyBoss Platform plugins. 3. Try activating the WPML String Translation plugin first. 4. Reactivate the BuddyBoss plugins. 5. Ensure all plugins are updated to their latest versions.
If this solution does not resolve the issue or seems outdated, 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 the problem persists, please open a new support ticket.
