In the review queue for approving new users, tomtjes reports seeing mixed-up information: standard user fields display data from a previously approved (and possibly deleted) user, while custom fields correctly reflect the new registrant. This inconsistency doesn’t appear in the Admin > Users > New view, where the new user is displayed correctly. codinghorror asks if the issue is reproducible, and tshenry confirms they reproduced it once on a test site using a specific sequence (signing up, approving, deleting, and reusing an email), but couldn’t replicate it again — suggesting the system may self-correct after handling a user. tomtjes adds that past occurrences involved declined bot registrations followed by corrupted data for the next legitimate user, though the most recent case didn’t follow that pattern. No consistent reproduction steps have been found, making debugging difficult.
When approving new users, I’ve been seeing mixed up info in the review queue. Here’s the latest example. All regular fields refer to the user that signed up before this new member. As the green checkmark shows, that user (a test user) had already been approved, so it shouldn’t appear in the review queue. The custom user fields though have information the actual new user entered during registration.
So… I was able to repro once on my test site that has had prior testing activity, but I haven’t been been able to repro again. Very frustrating!
@tomtjes can you provide consistent reproduction steps by chance? I’m wondering if handling a user once will kind of “flush” the system so to speak and get things back to normal.
Here’s one set of steps that I tried for example:
must approve users site setting enabled, and at least one custom user field in place
Sign up first user
email: email1@test.com
username: user1
name: User One
user field: test1
Approve first user
Delete first user
Sign up second user
email: email2@test.com
username: user2
name: User Two
user field: test2
Sign up third user
email: email1@test.com (reused since original account was deleted)
Thanks for looking into this!
Unfortunately, I haven’t found a pattern that could be reproduced. It happened before. At that time, it involved a bot that wanted to create an account, but was declined by me. The next legit user who registered had garbled data. Following registrations were fine until the case that I documented above. As far as I remember that case was not preceded by a declined registration.
