Quote:
Originally Posted by SauceHelmet07
Hey Pharaoh,
Not sure if this is due to the update or what, but the console says AdSQL is firing the ads, yet they aren't appearing in-game.
[snip]
Then it lists all the ads here and begins firing them.
L 03/11/2011 - 21:48:09: [adsql.smx] [Ads-QL] Firing Ad 4/15 [21:48:09]: s, {GREEN}Type {LIGHTGREEN}motd {GREEN}for a list of server rules., all, cstrike
|
Umm, is that really a lowercase "s" right before the ad text?
ie:
L 03/11/2011 - 21:48:09: [adsql.smx] [Ads-QL] Firing Ad 4/15 [21:48:09]:
s, {GREEN}Type {LIGHTGREEN}motd {GREEN}for a list of server rules., all, cstrike
if so, then my immediate guess is that the ad is not actually displaying (even though you see the "firing ad" message in debug log output) because it doesn't know what an "s" type ad is. It is supposed to be "S" (capital S).
Quote from the source code section responsible for displaying "say" type ads:
Code:
if (StrContains(sType, "S") != -1)
{
Did you manually edit ads in your database or something? I have checked all "legacy" ads in my database as well as new ones I have added through the newer web interface and don't have any "say" type ads (all but 1-2 of ours are say ads) that had the ad type set to lowercase "s". I have also edited several ads. They are all uppercase S. So I don't think this is a problem with the plugin or the web interface writing a lowercase "s" into the ad type field in the database. The most likely cause I can think of is that these ads were added/edited manually and you didn't put uppercase S's into the field.
You are probably going to have to go back and fix your ads.
PS: if you are using a different web interface to edit these ads besides mine, you'll need to take this up with whoever wrote the other interface.
Quote:
Originally Posted by SauceHelmet07
Edit: Just tried the plugin on another server, same exact issue. Only difference is console, it doesn't say Firing, it just says
[Ads-QL] Ad 2/13: s, {GREEN}Type {LIGHTGREEN}motd {GREEN}for a list of server rules., all, cstrike
|
The obvious explanation here is that you are running a different version of the plugin on that server which displays a different debug-level log message. See the
Changelog