You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The custom roles created on the main site, shows up on the subsite. For example level 3 custom role on main site, shows on subsite which only has level 1 and 2. Should we have a filter to disable this or handle it better as there may be more conflicts when it comes to 'overlapping' membership ID's.
To Reproduce
Steps to reproduce the behavior:
Install the Roles for Membership Add On individually on the main site and a subsite.
Create more level's on the main site than on the subsite. (i.e. 3 levels on main site, 2 levels on subsite - or even just make sure there is no overlapping ID's between the sites for this test).
Navigate to your subsite level settings and click edit, have a look at the role selector and notice roles from the main site showing up.
This is for sites that run PMPro individually on each site in the network (Do not use the Multisite Membership Add On for these tests).
Screenshots
In the above screenshot on the subsite, the "NEW!" (pmpro_role_2) level is on the main site and not the subsite.
Expected behavior
This needs more discussion, but should we isolate roles based on the site ID instead of registering the roles across all sites?
Isolating the problem (mark completed items with an [x]):
I have deactivated other plugins and confirmed this bug occurs when only Paid Memberships Pro plugin is active.
This bug happens with a default WordPress theme active, or Memberlite.
I can reproduce this bug consistently using the steps above.
The text was updated successfully, but these errors were encountered:
Describe the bug
The custom roles created on the main site, shows up on the subsite. For example level 3 custom role on main site, shows on subsite which only has level 1 and 2. Should we have a filter to disable this or handle it better as there may be more conflicts when it comes to 'overlapping' membership ID's.
To Reproduce
Steps to reproduce the behavior:
This is for sites that run PMPro individually on each site in the network (Do not use the Multisite Membership Add On for these tests).
Screenshots
In the above screenshot on the subsite, the "NEW!" (pmpro_role_2) level is on the main site and not the subsite.
Expected behavior
This needs more discussion, but should we isolate roles based on the site ID instead of registering the roles across all sites?
Isolating the problem (mark completed items with an [x]):
The text was updated successfully, but these errors were encountered: