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
If a user changes their level while pending approval for another level, details of the pending approval are not cleared from the database.
This can cause an incorrect count to display in the approvals notification badge.
To Reproduce
Steps to reproduce the behavior:
In a level group that does not allow multiple selections, set up levels that require admin approval
Complete checkout for a level in the group requiring approval.
Complete checkout for a different level in the group.
Search the usermeta db table for pmpro_approval_ entries associated with your user ID.
See that entries exist for the first level checkout
Expected behavior
If a user's level changes while pending approval, the previous level's pending approval data is cleared from the database.
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
WP 6.5.2
PMPro 3.0.3
PMPro Approvals 1.5.1
The text was updated successfully, but these errors were encountered:
Describe the bug
If a user changes their level while pending approval for another level, details of the pending approval are not cleared from the database.
This can cause an incorrect count to display in the approvals notification badge.
To Reproduce
Steps to reproduce the behavior:
pmpro_approval_
entries associated with your user ID.Expected behavior
If a user's level changes while pending approval, the previous level's pending approval data is cleared from the database.
Isolating the problem (mark completed items with an [x]):
WordPress Environment
The text was updated successfully, but these errors were encountered: