Open fearts opened 1 year ago
@rumblefrog Your commit https://github.com/sbpp/sourcebans-pp/commit/358d31e7345e700f1f5da0e55d9f5d889e2fe987 re-open this issue.
@rumblefrog Your commit 358d31e re-open this issue.
Hm wasn't thinking with that one. But I'm not sure if removing the isset would be a good solution; it's creating an erroneous message every time the page is visited, so I added it back.
Yea, with the newest release this is what it looks like with the fix Rush added.
![]()
Yea, with the newest release this is what it looks like with the fix Rush added.
That being said, warnings shouldn't be enabled in production environments. I'm not certain if that's configurable within NFO.
What are the steps to reproduce this issue?
If the punishment is not a Perm Mute/Gag then the Unmute/Ungag option does exist. Perm Bans have the Unban option so why do Perm Comms not have it? Without this option my head admins are unable to remove the punishment as I do not give them Delete/Edit permissions.
I'm using the php81 version of the webpanel.
Attached is a image demonstrating the issue. Thank you.