search

wid-tech / website

1 stars 0 forks source link

User 1326 displaying incorrectly in main members screen #71

Closed pamelatech closed 2 years ago

pamelatech commented 2 years ago

Describe the bug There are serious inconsistencies for a specific user. Joanne Mavridis (user #1326) is an Admin if I go look at her membership in Apex, but she shows up in the apex members page as having the "Apply for Membership" plan. If I look in her home chapter, she correctly shows up as a community member in her profile and the members page.

Database inconsistencies are concerning - @mcresilkstart do you have any idea why this would happen? I don't know how we could identify or fix these kinds of errors, it may be we can fix by modulating the plan but it is still very concerning

What kind of user are you? Site Admin

To Reproduce Steps to reproduce the behavior:

  1. Go to https://www.womeninidentity.org/onepage/profiles/joanne-mavridis/sections/membership
  2. Note she is an admin
  3. HEad to https://www.womeninidentity.org/onepage/members 4.Plan shows up as Apply for Membership

Expected behavior A clear and concise description of what you expected to happen.

Screenshots image

image image

mcresilkstart commented 2 years ago

@pamelatech that looks like a bug. If you look at membership history on details for her you see she was initially on the 'Apply for Membership' plan and then was moved to the community plan. The APEX members display is not correct for some reason. I will report this as a bug. Note that being an Admin is more of a user status than a plan. An admin typically exists with some kind of membership plan but doesn't have to have one.

mcresilkstart commented 2 years ago

@pamelatech I have logged this as a bug. However I note that this behaviour is not consistent. If you look at my test user Michael Creswell Test2 member number 1362 which started as an Apply for Membership and then got moved to Community member, this user is displayed correctly on the member list page. This user was added at a later date than your example. The problem that you found may be a hangover from something that is now fixed (bug fix of config fix).

hlflanagan commented 2 years ago

user no longer exists because of user import, so we can't reproduce it on our site. We'll close this on our side.