Confirmed Warning with ban = not a good reason

DevPunk

Member
Affected version
2
Why is a warning and the resulting ban (warning action) - not used the reason from the warning?
XF uses here, firmly burned into the code, a phrase that is useless.
Code:
$reason = strval(\XF::phrase('warning_ban_reason'));
:eek:

Totally stupid and for the user not understandable why he was banned.
 
While I agree the existing UX is poor, the ban may be triggered by an accumulation of points across multiple warnings. It might be nice to add a "reason" field to warning actions instead. I think it'd be ideal to be able to send warning emails as well, as even when sending a conversation a subsequently banned user will not be able to view the conversation and may have conversation emails disabled.

Though if you're concerned about the user experience, I find it's better to create a read-only usergroup and have warning actions add the user to that instead, and set up warning conversations.
 
Top Bottom