I am not sure if it would be because you would need a parameter in order to hide something from a banned user. And I think you only have those parameters about a user once they log in. Before that, they are simply anonymous users. You don't have anything to go on, so you can't hide the register/sign in option but this is me guessing.
Now, I am curious to learn as well.
I am not sure if it would be because you would need a parameter in order to hide something from a banned user. And I think you only have those parameters about a user once they log in.
This is exactly right if the user is banned based off of their username. The way the ban tool works makes this a slightly complicated question to answer.
In short, the ban tool provides you a series of options to base the ban on: User Name, User ID, Email Address, and IP Address. Additionally, the logic of the ban can be controlled with the check box titled "Match any of the above criteria."
This allows for a few different scenarios. Imagine scenario #1, I have user who is banned based off of their User Name, IP Address, and Email Address, and I leave the Match Any Criteria box unchecked. The ban will only be in place once the system sees the specified User Name (only happens at login), the IP Address, and the Email Address. We call this an "And" ban. X and Y and Z all need to be true. If any of those items don't match the fields input during the ban, the ban doesn't hold. If User Name and Email Address are inputs in this kind of ban, it can only be assessed after sign in.
Scenario #2, however, could potentially accomplish what you're looking to do. If I have the same inputs in my ban: User Name, IP Address, and Email Address but I do check the "Match Any Criteria" box, the ban is now an "Or" ban. X or Y or Z can be true and the ban holds. In this case, if the IP address is used as an input in the ban, the user is prevented from ever seeing the community at all, much less being able to sign in. The system triggers the ban message immediately upon seeing that IP address.
I'd be remiss without mentioning that Scenario #2 should be used with a lot of caution. An IP based "Or" ban can be really powerful, but can also sometimes catch users you didn't intended to ban. Imagine that you've banned someone accessing the community from their workplace or university, one where they share their IP Address with a large number of people. If you tell the ban logic it can prevent access based solely off of an IP Address, anyone who happens to share that IP Address is also banned. This is usually an edge case, but it's worth being wary of.
Hi, thanks for commitment.
The reason I'm asking this tricky question is that I got this solution adviced by Support in Case Portal.
I reported an issue where if banned user try to sign in/log in, he is redirected to blank page, "http status 403"
Oh, but then that page is populated after a banned user tries to sign in, right? It is not like you are hiding the sign in option.
Perhaps there is a way to show a custom page when user logging in matches status = banned...