Background of the issue:
I'm using Paid Memberships Pro (PMPRO) with WooCommerce Subscriptions to sell membership levels to users. These memberships are also being used to restrict content throughout the website, especially some BuddyBoss social and access features. Everything works fine for the main language, English.
Symptoms:
The restricted content does not apply to the French side of the website. It seems like the membership levels are not synced between both languages, preventing restricted content from working. I need to enable content restriction manually and separately for the French backend, which is not feasible for BuddyBoss social features.
Questions:
Can you help me sync membership levels for both languages so that restricted content works on the French side of the website?
I understand the issue you're facing. It seems that the translation preference for the custom fields, containing the restriction rules might not be set to "Copy"(to sync across languages), which is why the restriction rules aren’t being applied correctly to the French language.
If you can identify the field where you’re adding the restrictions (by using the hidden link">browser inspector to check the field name), try the following steps to see if they resolve the issue:
- Go to WPML > Settings and scroll down to the 'Custom Field Translation' section.
- Click on the "Show system fields" link.
- After the page refreshes, scroll back to the 'Custom Field Translation' section and enter the field name in the search box.
- If the field appears in the results, set its translation preference to "Copy." Do this for all fields where you’re adding the rules.
- Save the changes.
- Open the page where you’ve applied the restrictions, make a small change to the title, and save it.
- Update the translation.
Please let me know if the information helps or if you need further assistance in this matter. I will be happy to help.
Thank you for your response, this is gladly appreciated.
I've looked into what you said and i found some potential fields but i'm really not sure on how to manage this without breaking the website.
Let me exlain even further the issue here,
Here is the plugin associated with Memberships and Users :
- Woocommerce Subscriptions (WOOSUB)
- Paid Membership Pro (PMPRO)
- WPML
- Buddyboss theme and Buddyboss Pro
For a user to register, they need to buy a WOOCOMMERCE SUBSCRIPTION PRODUCT, THE WOOSUB PRODUCT assign the PMPRO MEMBERSHIP LEVEL to the user. The PMPRO MEMBERSHIP LEVEL then assign the BUDDYBOSS PROFILE TYPE (Member_type) to the user and finally the BUDDYBOSS PROFILE TYPE assign the WORDPRESS ROLE to the user.
PMPRO Does also apply restrict content related to Buddyboss features.
Everything works fine in ENGLISH but not in FRENCH. Its like as you said, something is not being copied somewhere preventing from restricted content features to be applied.
I'm just not sure on what to COPY to make sure that everything works fine on both languages.
PMPRO membership levels doesnt need a translation, i just need the membership levels to be sync in both languages for them to apply the good member/profile type of Buddyboss while keeping the same restricted content on pages and buddyboss features.
Profile/Member type of Buddyboss needs to be translated but only the text on the frontend not their database ID, it needs to be sync on both languages.
The woocommerce subscription products are already translated
Wordpress Role doesnt need translation just to be sync
So when somebody is registering and buying a membership, i just want to make sure that the attribution is well done such as :
Woosub product > Membership levels (PMPRO) > Profile/Member Type (Buddyboss) > WordPress Role
I've reach out to Pmpro free support and let them know your thoughts
I think i might found a solution by myself since PMPRO is not compatible with WPML, there is a default social control options provided by BUDDYBOSS based on WORDPRESS Roles that would solve my problem for BUDDYBOSS features.
About restricted pages, i think i might use WPFUSION access control instead.
And use AUTOMATORWP to assign Profile/Member Type if a WOOCOMMERCE SUBSCRIPTION is bought by a user.
I'll let you know how it goes tomorrow! Thanks again! If you have other solution let me know!
If you're not translating the Membership Level, simply copying the Membership settings from the Subscription product to the French subscription product should work. This way, users who purchase the French subscription will have the same restrictions as those applied to the default Subscription product.
As you know, the PMPRO Membership plugin is currently not compatible with WPML, so I'm not entirely sure about the exact name of the field that stores the Membership information. However, setting that field's translation preference to "Copy" should ensure that the Membership data is copied over to the translated product.
You can try out the suggestion as well as the solution you found, and feel free to reach out if you have any questions or need further clarification. I'm here to help!
Sorry for the delay, i found a solution, i've uninstalled PMPRO
About restricted pages, i use WPFUSION access control instead.
And use AUTOMATORWP to assign Profile/Member Type and WordPress role if a WOOCOMMERCE SUBSCRIPTION is bought or switched by a user.
The only issue that i would love to solve now is translating Buddyboss Profile Type while conserving the same ID in the Database. Is it possible?
Because when i've looked into *POST TYPE TRANSLATIONS*, i saw the profile type as an option but when i checked to *TRANSLATABLE* it does create separate Profile type (one in english and the other in french)
I would love to translate without having to duplicate in the other language the profile type.
When you translate a post or page using WPML, a separate instance of that post or page is created in the database with a different ID. If you want to translate BuddyPress profile types without changing the ID, unfortunately, this won’t be possible.
If you want, you can set the translation preference for the profile type to "Translatable - use translation if available or fallback to default language." This will allow the default profile type to appear in the translation, ensuring everything continues to work smoothly and in sync.
However, If you translate the Profile Type, you'll need to configure the translated profile type the same way as the default profile.
I hope you can understand. Please feel free to let me know if you have any other queries or need clarification. I will be happy to help.
I've tried your solution, but it still creates duplicated profile types for all languages preventing any good syncing or good functionalty with other plugins as well as preventing members to be shown on Buddyboss Members page because the profile type are not well configured this way.
I just need to translate it as a string without having to duplicate just like a normal string translation. I saw a post related to this issue and the guy seems to have the same problem as me.
hidden link
Now the only for me to make it work is too write the label of the profile type in both languages and it can be fine for a DOUBLE language website but i'm planning to make a third language so it cant stay this way.
Is there any way to translate the label only shown at frontend?
I've created a new Profile Type name : TEST in ENGLISH and TESTEI in FRENCH.
On a single profile, the profile type is being shown as ENGLISH whatever happens
On the member search page, no member is being shown anymore
On the backend, User is only assign to the default profile type in english but not in french since a user can only have ONE PROFILE TYPE
It really needs to be synced while the label on the frontend being translated!
Hello There,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
Thank you for providing the details. If the issue you're experiencing is the same as the one mentioned in the other ticket you shared, have you tried implementing the solution suggested in this response?
I'd also like to inform you that we are aware of an issue with BuddyPress profile types where the profile fields do not appear translated on the frontend. Please refer to the Errata below for more details.
