User stuck in 'staged' status

bug
1

I have a user whose account was originally created as a staged account via an import from another system.

Recently, they logged in and created a new topic.

But they still show up as a staged user, and I cannot @mention them.

I do not see any way in the Admin UI to force them to become “unstaged”.

Potentially relevant site settings:

  1. Google Login enabled
  2. Local logins disabled
  3. Email whitelist domains (1)

Currently running version v1.5.0.beta13b +38 (67a5fc39ded9f661974b6e06b109c75b50d3a1b1)

2

Can’t you delete the staged account? Sounds like the emails don’t match?

3

As far as I can tell there is only a single account for this user with that one email address.

On their user page in the Admin section, the “Email” field value matches the address in the “Logins” filed

eg:

Email: foo@example.com
Logins: Google(foo@example.com)

4

I think @zogstrip will need to have a look

1 Like
5

@zogstrip feel free to reach out here or via PM if you want more details that I can help get via logs or db queries, etc.

6

I’ll have to try login in using the same email address using OAuth, but in the meantime, you can fix it with

cd /var/discourse
./launcher c app
User.where(email: "foo@example.com").update_all(staged: false)
1 Like
7

Thanks, I have found other users in this state, so I’ll use this workaround for now…

Here’s what I’m doing to catch them all periodically:

User.where.not(previous_visit_at: nil).where(staged: true).update_all(staged: false)

This time it updated 29 users…

1 Like
8

Just pushed a fix :banana:

https://github.com/discourse/discourse/commit/841f36b0589d9e5aa0bbfcd328b0c3a2d7f795b0

4 Likes
9

This topic was automatically closed after 12 hours. New replies are no longer allowed.