rumblefrog
rumblefrog
Neat, there are a lot of problems with legacy Sourceban that we discover as we build on top of it; it's only a matter of time before a complete rewrite.
This is a pretty edge case scenario. Wouldn't it be better to wait for the upstream fix? It looks like it's already done and waiting to resolve the conflicts.
Is there a reason why you can't query the database in the plugin would otherwise be using the native? I'm not entirely sure if this feature feasible or have enough...
There's something like this for SourceComms module, but not for bans. You could also use separate database :P
I'll take a stab at this.
Didn't realize how messy the original sourceban code is until I got started.
Would you mind providing the example command you used?
Perhaps with the upcoming templating engine change, people will start making mobile friendly themes :3
Edit Ban Details Fatal error: Uncaught Error: Cannot use object of type ADORecordSet_mysqli as array
The demo system has been funky in the past, so I'm not surprised if this does happen. This means we need to rewrite this portion of the system as well.
Can you try to replicate with the default theme