CUNY Academic Commons

Boone Gorges wrote:

Hi Luke - Somehow you ended up with multiple memberships records in the JITP group. One of the group memberships listed you as an admin, the other did not. The Group Admins part of the page was getting its info from the first of these records, while your menu was being built from the other one. Thus the discrepancy. I've deleted the duplicate, and you should be good to go - please verify.

No-- I'm no longer in the group. Doesn't show up in my group listing, and I have option to join when I go to group page (http://commons.gc.cuny.edu/groups/journal-of-interactive-technology-and-pedagogy-public-group/).

As to how this happened: I don't know for sure. Something similar happened in https://redmine.gc.cuny.edu/issues/6091#note-6, but the circumstances were slightly different. Luke, can you give me any additional information that you can recall about changes to your membership today? Who promoted you? How? Were there any mistakes - like an accidental removal from the group, or an incorrect invitation - involved in the process?

I joined group 10/18 (shows in activity stream -- http://commons.gc.cuny.edu/members/lwaltzer/activity/445661/), and Ben Miller bumped me up to admin soon after. I believe Ben also decoupled the group from the JITP site, where I am an admin-- could that have been a source of the duplication?

No other elements of the interaction seemed odd.

No-- I'm no longer in the group.

OK, this part is fixed now. Sorry about that. Previously, there were two membership records:

1. An unconfirmed invitation to join the group, sent by Ben Miller. This record had you listed as a group admin.
2. A regular group membership (self-join), with a timestamp about 90 minutes earlier than 1.

The one I deleted yesterday was #2, which left you with an unconfirmed invitation. I've confirmed it and now see you on the list of group members.

Trying to piece this together: You joined the group on your own, which created 2. Ben then promoted you. Promotion is supposed to work by fetching the existing group membership for that user, changing the status, and resaving. But in this case, a new record was created. This sounds like it could be a cache problem, but our current version of BuddyPress doesn't have any persistent caching for individual group memberships (it's coming in BP 2.7). This kind of bug can also happen when there's a lag during MySQL replication, but we don't use any live replication on the Commons.

Ray, I've copied you as a watcher in case anything jumps to mind.