Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additional Roles removed when updating user from the Member Edit page. #2959

Open
3 tasks done
ipokkel opened this issue Apr 16, 2024 · 1 comment
Open
3 tasks done
Assignees

Comments

@ipokkel
Copy link
Member

ipokkel commented Apr 16, 2024

Describe the bug
If a user has more than one role assigned the additional roles assigned to the user are removed when updating a user from the Member Edit page.

To Reproduce
Steps to reproduce the behavior:

  1. Install PMPro Roles Add On.
  2. Create a level group that allows choosing multiple levels from the group and create two membership levels in this group.
  3. Check out as a test user for both of these levels and query the roles assigned to this user to confirm that the user has both membership-level roles assigned.
  4. Navigate to Memberships > Members and select to edit this member. Observe that only one of the roles is selected as the role for the user.
  5. Click on Update User Info and query the roles assigned to this user to confirm that the user now only has the role assigned that was selected in the User Info tab of the Edit Member page.

Expected behavior
Additional user roles should remain assigned to a user when updating the member on the Member Edit page.

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.

WordPress Environment

- WordPress 6.5.2
- Paid Memberships Pro 3.0.2

Moderators (only)
#561648

@MaximilianoRicoTabo
Copy link
Contributor

Same for this one, with commit below that make remove dropdown and make it a disabled component is this issue still valid ? 64c4ee2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants