Not sure if this is a bug or not, but when a post needs to be approved, and I opt to reject it (as it doesn’t really fit the type of content we want), it leaves the user as blocked and the rejected post is not associated to the user anymore (likely related to the deleted posts not being associated to the user – so this part may be fixed in a later commit). We are running Discourse 1.5.0.beta1 - GitHub - discourse/discourse: A platform for community discussion. Free, open, simple. · GitHub version 4d78a7b1d5129998015b8582cbbae34b4e4bc8ca Is anyone else running into this? Edit: Based on reviewing the commit for fixing deleted user action associations, it seems we have that fix in our version, but it doesn’t work when rejecting a post that needs to be approved.

[image] cpradio: when a post needs to be approved, and I opt to reject it (as it doesn’t really fit the type of content we want), it leaves the user as blocked and the rejected post is not associated to the user anymore This seems correct as designed – when you reject a first post by a user, you are implicitly rejecting that user, too. This is really a question for @sam since he designed the feature. I think the workflow you’re using is a bit wrong here. You should accept the post, then delete it or message the user to let them know “that post wasn’t spam, but it isn’t something we want, either” I told @sam that copy on the page was wrong, the button should say “Delete Spam”, but it was never changed..

Yep, but we have them set to [image] But when you reject a post it catches, it leaves the person blocked even though you don’t want the post to be made, but you don’t see a reason to delete/ban the user. We were anticipating that Approve/Reject would unblock the user and either show/delete the post, and delete would delete the post and ban the user. However, Approve does that (good), Reject doesn’t (leaves user blocked, but no indication they have a deleted post), and Delete does what you’d expect too (destroys the entire user).

Okay, that’s a fair response. We’re trying to figure out how to properly use it, so if that is the intention, I’m good with that, just need to understand it better, now that we have it in a real scenario setting. :smile: Thanks for the clarification. I think I understand how it works now. Should rejecting a post still show that post as related to that user? IE: Deleted post for that user?

[image] Regardless, it is quite unclear how this should work and @cpradio has a point… some key changes need to happen: Delete User should be changed to “Delete Spammer” ASAP Approve unblocks the user and posts the post, that seems clear. Reject.. rejects the post and keeps the user blocked? Any comments here @sam?

Yeah Reject is super weird, if a user is blocked we should not allow that option imo.

I would just like to add a 4th item Reject deletes the post, but the deleted post isn’t attributed to its owner. It is in limbo.

Is that current behavior or desired behavior?

[image] riking: Is that current behavior or desired behavior? Not sure, I’d prefer deleted posts remain attributed to the person who created them. Otherwise, as staff, when I visit that user’s page, I can’t see what posts have been deleted for that user (sometimes this helps with decision making on how many more chances they get).

Is there any difference when the post is the OP (i.e. the Topic) vs. a reply?

[image] Mittineague: Is there any difference when the post is the OP (i.e. the Topic) vs. a reply? Not 100% sure, if I get time I may try both of those at home, but to my knowledge and best recollection, no there isn’t.

So I’m not sure if this should go under a new topic or along the lines with this one, but we’ve had one complaint arising around Needs Approval lately (beyond the Reject button). Context. It is hard to identify the context of the post/reply (when it is a post/reply to an existing topic). We can visit the existing topic, but we have no clues to if it is a reply to a prior post above, or just to the topic as a whole at the end. We don’t really know where in the chain of responses this person would have fit as there isn’t any indication. I sort of wish it worked more like Akismet, where it has the post in the stream, but deleted, so we can visit it and see these clues.

Needs Approved Reject doesn't Unblock or associated the rejected post with the user

Product Support

cpradio (cpradio) October 2, 2015, 10:13am 12

I would just like to add a 4th item

Reject deletes the post, but the deleted post isn’t attributed to its owner. It is in limbo.

Topic		Replies	Views
Approving or rejecting what? The flag or the post? Feature	10	3095	April 23, 2019
Add reason for rejection of a post Feature moderation , completed , review-queue	33	5965	October 13, 2023
End user pre-approval queue experience can be much improved Feature	16	3869	February 7, 2022
Needs Approval doesn't Log Reject Feature	11	1183	June 11, 2019
Pre-approval queue is too hidden UX	16	2156	October 23, 2017

Needs Approved Reject doesn't Unblock or associated the rejected post with the user

Related topics