SecurePoll needs a UserMergeAccountFields subscriber to support UserMerge.
Version: unspecified
Severity: enhancement
Description
Description
Details
Details
- Reference
- bz67777
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Resolved | Jdforrester-WMF | T69758 Identify extensions that need updates to work with user merging | ||
| Declined | None | T69777 Add UserMerge support to SecurePoll | ||
| · · · |
Event Timeline
Comment Actions
Should we even do this? We probably shouldn't be altering the results of previous votes...
securepoll_elections has el_owner
securepoll_voters has voter_name (don't see any renameuser support) - there are also tables referencing voter_id if we merge these rows
securepoll_lists has li_member
Comment Actions
I sent an email to Philippe, Jamesofur, and Tim Starling asking for their input on this.
Comment Actions
Talking to Philippe I think this is an edge case that isn't worth worrying too much about. Right now we don't change it for renames (for example it still shows my test votes from last year as Jalexander) and it is unlikely that we would be able to do much if we discovered a historic case of socking.
We'd also have to think about exactly how to 'show' it and there is some usefulness to having the historic record be unchanged "at this time and date this username from this wiki voted" etc. Not sure the benefits outweigh the costs.