[driz]

Just want to say, I've been running this fork for a few days now and it's been great. We have a mix of gmod servers, css/csgo servers running the latest official in game plugin and a few dev servers running the 1.5.2F in game plugin. Everything is working fantastically (we haven't tried sourcecomms yet)

I'm running this on the following:
CentOS 7.1.1503
kernel 3.10.0-229.4.2.el7.x86_64
PHP Version 5.6.10
Ver 15.1 Distrib 10.1.5-MariaDB
nginx version: nginx/1.8.0


I can't think of any other requirements for this so i listed what I remembered checking. It's all running great aside from a minor tweak I had to make to the apodb stuff that i referenced earlier on.

thanks for your great work; hopefully maybe you might take on sb2 one day, the thought of multiple groups per user gives me a lot of ideas for other applications

[Alice.bnd]

Hi.
I have a problem after TF2 Update 7/2.

L 07/04/2015 - 00:05:06: [admin-flatfile.smx] Error(s) detected parsing addons/sourcemod/configs/admins.cfg
L 07/04/2015 - 00:05:06: [admin-flatfile.smx] (line Unknown group "Alice's System Administrators"
L 07/04/2015 - 00:05:06: [admin-flatfile.smx] (line 33) Unknown group "Alice's Administrators"
L 07/04/2015 - 00:05:06: [admin-flatfile.smx] (line 39) Unknown group "Alice's Administrators"
L 07/04/2015 - 00:05:06: [admin-flatfile.smx] (line 45) Unknown group "Alice's Administrators"
...

[scso1502]

According to several devs here on Allied Modders, the admin-flatfile.smx problem is the result of a coding conflict between the TF2 game code and SourceBans that recently reared it's ugly head. It's been looming out there for sometime but finally revealed itself. There is more info about it starting at post #63 of this thread:

https://forums.alliedmods.net/showth...=265635&page=7

One fix is to use the admin-flat-file posted in the below thread by friagram, which should hopefully fix your problem:

https://forums.alliedmods.net/showpo...7&postcount=94

Good luck!

[scso1502]

I made a copy of my SourceBans 1.4.11 web folder. I downloaded a fresh copy of 1.5.2F. I uploaded the files to my webserver and set the permissions. I put the config.php from my SourceBans 1.4.11 back where it belongs with the 1.5.2F files. I ran the updater to upgrade from 1.4.11. All seemed to go well with the updater but now when attempting to access my SourceBans webpage, I get this error:

Theme Error: sb_fun is not a valid theme. Must have a valid theme.conf.php file.

I looked at my theme.conf.php file and it shows this:

<?php /** * theme.conf.php * * This file will set some stuff about our theme * @author IceMan * @Modified By: Sarabveer(VEER™) * @version 1.2-S * @copyright TF2 Romania (www.tf2.ro) * @package TF2 Romania * @link http://www.tf2.ro */ // Set the name of this theme here define('theme_name', "SourceBans Default Theme"); // Set the author of this theme here define('theme_author', "IceMan, Sarabveer(VEER™)"); // Set the version of the theme here define('theme_version', "1.2-S"); // Set the link of the theme here define('theme_link', "https://forums.alliedmods.net/showthread.php?t=252533"); // Set the screenshot filename for your theme (must be inside your theme folder) // Must be: 250px wide X 170px High define('theme_screenshot', "screenshot.jpg"); ?>

Why is it looking for sb_fun theme? If I recall correctly, that was an old theme in the dev stages I saw somewhere.

I've reverted everything back to 1.4.11 for now.

HELP!

[Sarabveer]

Originally Posted by scso1502 I made a copy of my SourceBans 1.4.11 web folder. I downloaded a fresh copy of 1.5.2F. I uploaded the files to my webserver and set the permissions. I put the config.php from my SourceBans 1.4.11 back where it belongs with the 1.5.2F files. I ran the updater to upgrade from 1.4.11. All seemed to go well with the updater but now when attempting to access my SourceBans webpage, I get this error: I looked at my theme.conf.php file and it shows this: Why is it looking for sb_fun theme? If I recall correctly, that was an old theme in the dev stages I saw somewhere. I've reverted everything back to 1.4.1 for now. HELP!

What folder is the current theme you use for 1.4.11

It wouldn't need to look there if it isn't set as the theme.

[scso1502]

Ok, I figured it out. Apparently the theme settings must be stored in the database. If you use a custom theme for your SourceBans website and the theme doesn't exist on the fresh install, the website won't open and reports the error I listed above.

I have a custom theme called "sbfun" on my old 1.4 install that was set to the current theme. I reset the theme on the old 1.4 install back to the stock dark theme then switched back to the new 1.5.2F install and it works perfect now.

For those of you switching to the new version, make sure you reset your theme before the switch so it works. I suppose you could copy your custom theme over but it wasn't worth the risk for me to attempt this right now.

Thanks for the great work keeping SourceBans alive Sarabveer! I really appreciate it!

[scso1502]

Here are some very minor fixes for you to include in your next hotfix good sir. Not trying to be nit picky, just trying to help you tweak the little stuff you probably haven't had time to deal with. The software looks and works great!

Proposed Fix list:

The below theme issues apply to all the themes as far as I can tell.

1. On the Commslist page, the overview bar has the word "Communications Blocklist Overview" misspelled as "Communicatinons Blocklist Overview"

2. On the Admin Panel Page under Protest Information - I recommend you change "Total Protests" to "Pending Protests"

3. Also on the Admin Panel Page under Submission Information - I recommend you change "Total Submissions" to "Pending Submissions"

4. Also on the Admin Panel Page under Ban Information - suggest you change "Connection blocks" to "Connections blocked"

5. Also on the Admin Panel Page under Ban Information - The Total Demo Size is "0" for me however I have quite a few demos so apparently this feature doesn't work.

6. On the add New Admins page, the second field "Admin Steam ID / Community ID" wraps "ID" to the next line

FEATURE REQUEST FOR A LATER VERSION:

1. Add a tab somewhere to view the full blocked player list. Having that would be very helpful

Thanks again for all your hard work! Love it!

[Sarabveer]

Originally Posted by scso1502 Here are some very minor fixes for you to include in your next hotfix good sir. Not trying to be nit picky, just trying to help you tweak the little stuff you probably haven't had time to deal with. The software looks and works great! Proposed Fix list: The below theme issues apply to all the themes as far as I can tell. 1. On the Commslist page, the overview bar has the word "Communications Blocklist Overview" misspelled as "Communicatinons Blocklist Overview" 2. On the Admin Panel Page under Protest Information - I recommend you change "Total Protests" to "Pending Protests" 3. Also on the Admin Panel Page under Submission Information - I recommend you change "Total Submissions" to "Pending Submissions" 4. Also on the Admin Panel Page under Ban Information - suggest you change "Connection blocks" to "Connections blocked" 5. Also on the Admin Panel Page under Ban Information - The Total Demo Size is "0" for me however I have quite a few demos so apparently this feature doesn't work. 6. On the add New Admins page, the second field "Admin Steam ID / Community ID" wraps "ID" to the next line FEATURE REQUEST FOR A LATER VERSION: 1. Add a tab somewhere to view the full blocked player list. Having that would be very helpful Thanks again for all your hard work! Love it!

Ok, I did everything except #5, I don't get what ur saying, same thing with the feature request.

[Phaiz]

Originally Posted by scso1502 According to several devs here on Allied Modders, the admin-flatfile.smx problem is the result of a coding conflict between the TF2 game code and SourceBans that recently reared it's ugly head. It's been looming out there for sometime but finally revealed itself. There is more info about it starting at post #63 of this thread: https://forums.alliedmods.net/showth...=265635&page=7 One fix is to use the admin-flat-file posted in the below thread by friagram, which should hopefully fix your problem: https://forums.alliedmods.net/showpo...7&postcount=94 Good luck!

Can confirm this fixes the issue but according to other sources, the problem is Sourcebans

[Sarabveer]

Originally Posted by Phaiz Can confirm this fixes the issue but according to other sources, the problem is Sourcebans

It's How SB uses KeyValues to insert admins, and that has problems with upper and lowing case letters.

I never got the error on my windows servers, just Linux.