Old user suspension reasons have gone missing

Not going to post a full report here, as I have no repro steps or real details, but I just noticed that Reason field for suspended users has gone blank. I have no date as to when this occurred, but we have 3 suspended users on our instance and at least 2 of them has suspension reasons the last time I viewed their profile. It is not listed on their public profile, nor on their admin page.

3 Likes

Probably a bug based on reorganizing the user page @sam.

3 Likes

Not able to repro this on latest version.

Also, relevant code looks OK to me… :confused:

1 Like

Here’s one of ours (could this be another admin vs moderator issue? I am a mod, not admin…):

I am about 95% certain that it used to say “Banned for repeated violations” or something to that effect.

1 Like

Just verified locally that moderator is also able to view suspension reason.

As an admin when I visit: http://discourse.stonehearth.net/admin/users/epicdwarf – I am not able to view the suspension reason either, so I am sure this is not a user page issue.

1 Like

Agreed, I don’t see the reason on either page. I am going to PM the admin who suspended the user to see if she remembers. Mind if I include you on the PM (over on my site)?

2 Likes

Sure, go ahead! :slightly_smiling:

2 Likes

@techAPJ, I have confirmed that at least one of the users definitely had a suspension reason previously.

Happy New Year!

3 Likes

So this only happens for uses who are suspended multiple times?

1 Like

No. They were only suspended once (to the best of my knowledge). All of the users suspended (3 of them) were essentially suspended indefinitely (over 40 years each). I can add you to the PM over at Stonehearth if you would like…

1 Like

Is there any way you can reproduce this issue even on your site (create a sock puppet?)

I’m honestly not sure. I can certainly try creating a user and suspending it, but seeing as I have no idea when their suspension reasons disappeared, I am not sure it will work. Will try later today…

I can confirm this bug exists.

On April 17th 2015 I took a screenshot of a suspended user’s public profile with the specific reason “Use of multiple accounts detected”. The user was at that time given a many year suspension until the year 2289.

I’ll have to hide the username and other content but this is what it looked at the time (April 2015):

And this is what it looks like now:

Additionally in the admin section the reason is not shown:

This user has been suspended once, no other action has been taken against this account.

There are no additional plugins installed in this Discourse instance.

Standard updates applied, currently running Discourse 1.5.0.beta7 - version 0e2ded278db74c7446af83cc39bb5cd66ee50fda.

2 Likes

I am wondering if this is an open bug or a messed up migration, can you repro?

1 Like

I am unable to repro.

###This is what I tried

  1. Created new user account.
  2. Suspended that user account for 1000 days with message “Suspended user test”

###Results - works as expected

  • On suspension the user was successfully automatically logged out.
  • Admin page looks like this:
  • Public profile page for admin looks like this:
  • Public profile page for unauthenticated user looks like this:

Has to be a migration artifact. So in that case @jomaxro the workaround is to unsuspend the user, then re-suspend them.

A migration artifact from what? A Discourse update?

1 Like

Assuming you don’t have dozens of long-term suspended users :wink: the easiest quick fix is to unsuspend and re-suspend the (I am assuming) one or two users this applies to.

I wonder when this began because we have a TON (more than 200, probably more than 500) of suspended users and I’d hate to see those reasons go. So if you wanted, you could probably take a backup of our instance and run it through a migration to see what happens when you update it to latest.

I have well over 100 in one instance - but that doesn’t bother me.

Question: I take it there are no email notifications when a user is un-suspended / suspended again?