[DarkDeviL]

Originally Posted by SmackDaddy I haven't converted/upgraded to it yet -- just wanted to make sure there was still "admin ability" if the database was down....

Last two lines of THIS ONE still applies:

Originally Posted by arne1288 If your SourceBans database is constantly down so you really feel like you need the files, then you should switch to another - more professional - hosting provider. And if you really wish to run using files, well, then SourceBans isn't the thing you wish to run.

[Synthax]

Any chance of the addition of a "current name" and "banned as" kind of thing being added? Maybe with admins as well to keep track of names and make things easier. This could be polled periodically to keep server load down.

[sneaK]

Hey Sarabveer,

I'm using the packaged sourcesleuth in conjunction with the older 1.5.2 version (gotta update web still). It was working just fine up until recently, where if SourceSleuth detects an alternate account, bans it, but pops this error and never gets written into the database:

L 09/14/2015 - 23:33:37: [sourcebans.smx] Verify Insert Query Failed: Out of range value for column 'ends' at row 1

Any thoughts on how to solve this? Thanks!

[Sarabveer]

Originally Posted by blackhawk74 Hey Sarabveer, I'm using the packaged sourcesleuth in conjunction with the older 1.5.2 version (gotta update web still). It was working just fine up until recently, where if SourceSleuth detects an alternate account, bans it, but pops this error and never gets written into the database: L 09/14/2015 - 23:33:37: [sourcebans.smx] Verify Insert Query Failed: Out of range value for column 'ends' at row 1 Any thoughts on how to solve this? Thanks!

Use the 1.5.3 plugin.

[sneaK]

Originally Posted by Sarabveer Use the 1.5.3 plugin.

That did the trick, thank you!

[BBG_Theory]

Hey Sarabveer, I know you said the STEAMAPIKEY is just a placeholder for now,

so that does mean that the steam login is not able to work yet?

SELECT aid,password FROM sb_admins WHERE authid = 'STEAM_0:0:19517283'; 
Warning:  Cannot modify header information - headers already sent by (output started at /home/bigbang/public_html/sourcebans/steamopenid.php:63) in /home/bigbang/public_html/sourcebans/steamopenid.php on line 68

Warning:  Cannot modify header information - headers already sent by (output started at /home/bigbang/public_html/sourcebans/steamopenid.php:63) in /home/bigbang/public_html/sourcebans/steamopenid.php on line 69

Warning:  Cannot modify header information - headers already sent by (output started at /home/bigbang/public_html/sourcebans/steamopenid.php:63) in /home/bigbang/public_html/sourcebans/steamopenid.php on line 78

[DarkDeviL]

Originally Posted by BBG_Theory Hey Sarabveer, I know you said the STEAMAPIKEY is just a placeholder for now, so that does mean that the steam login is not able to work yet? SELECT aid,password FROM sb_admins WHERE authid = 'STEAM_0:0:19517283'; Warning: Cannot modify header information - headers already sent by (output started at /home/bigbang/public_html/sourcebans/steamopenid.php:63) in /home/bigbang/public_html/sourcebans/steamopenid.php on line 68 Warning: Cannot modify header information - headers already sent by (output started at /home/bigbang/public_html/sourcebans/steamopenid.php:63) in /home/bigbang/public_html/sourcebans/steamopenid.php on line 69 Warning: Cannot modify header information - headers already sent by (output started at /home/bigbang/public_html/sourcebans/steamopenid.php:63) in /home/bigbang/public_html/sourcebans/steamopenid.php on line 78

Steam Login button doesn't require an API key to work.

Your issue is different, steamopenid.php is sending data before sending header() calls, as the warning says.

Line 63 of steamopenid.php:

echo "SELECT aid,password FROM " .$prfx ."admins WHERE authid = '" .$data ."'; ";

Remove it, and try again.

[BBG_Theory]

omg, you are correct.


Why did I have to remove that and others don't?

thanks however, as it does seem to work.

thanks to Sarabveer and arne1288 for the help. Seems like a saw another php warning somewhere, but I'll post that if I see it again

[Schpraaankiii]

My serveradmins are reporting issues after the latest CSGO update. They can not seam to ban users anymore.
Sourcebans is still running perfectly and the accessflags are working fine.

I'm not sure if this issue is just with !ban /ban commands in textchat our console bans as well.

[irepz]

Still not able to login through steam after a 10th install, openid just saying 'error'...

Also another more annoying bug;
Admins rights aren't loaded on servers :

06 "SourceBans: Admin Config Loader" (1.5.3) by AlliedModders LLC, Sarabveer(VEER™)

Maybe this output could help :

for i in `ls |grep sb_admin`;do echo $i ; cat $i;done
sb_admin_groups.cfg
"Groups"
{
        "server_modo"
        {
                "flags"         "abcdefgjklopqz"
                "immunity"              "90"
                "Overrides"
                {
                        "sm_slap"               "allow"
                        "sm_mute"               "allow"
                }
        }
        "Donators"
        {
                "flags"         "akop"
        }
        "Slot_Only"
        {
                "flags"         "a"
        }
        "server_trialadmin"
        {
                "flags"         "abcdfgr"
                "Overrides"
                {
                        "sm_mute"               "allow"
                        "sm_slap"               "allow"
                }
        }
}
sb_admins.cfg
"Admins"
{
}

I guess sb_admins.cfg should be populated with admins steamid.