[zeroibis]

I keep getting:
L 03/24/2012 - 134:47: [crashlogger.smx] Can't select database
L 03/24/2012 - 134:47: [SM] Native "SQL_FastQuery" reported: Invalid database Handle 0 (error: 4)
L 03/24/2012 - 134:47: [SM] Displaying call stack trace for plugin "crashlogger.smx":
L 03/24/2012 - 134:47: [SM] [0] Line 74, crashlogger.sp::createdbtables()
L 03/24/2012 - 134:47: [SM] [1] Line 19, crashlogger.sp::OnPluginStart()

[snelvuur]

@zeroibis: how do you mean?

[zeroibis]

NVM I realized that you need to tell it to connect to the same database you use for the webpages.

[zeroibis]

Finally got around to getting this and now for the feature requests:

• Filters for admin activity
  • Server
  • Time
  • Plugin
• Filters for Active plugins
  • Only show plugins that appear on all server
  • Select what servers to compare
  • Only show plugins that have different versions on multiple servers

Could we get these options added in? I think it can really expand the power of this plugin if we are able to have these filters. It will make managing data a lot easier.

[zeroibis]

What is the Plugin Checker page for and how to I use it correctly. I tried testing it out but then some of the plugins disappeared and now I am worried I may have messed something up.

I edited the database to restore what I did. Then I entered the thread id of a mod like lets say weapon_restrict to be 105219. The mod then vanishes from the list on the plugin checker as I assume it should. However it still says No plugins are outdated, your a champ! when I weapon_restrict is outdated.

How am I supposed to use this function?

[zeroibis]

OK I understand now that I was supposed to run a cron for the check. After doing that I found some bugs:

• Plugin link does not work
• Plugin compares the wrong information

I find that it outputs for example:

Plugin |Version |Current Version
cheer.smx | 3.0.8 | 1.3

However what it is really doing is comparing the two plugins that I did enter data for which have the current versions of 3.0.8 and 1.3.

[zeroibis]

I realized that this "fix" should better be described as a way to switch over to use p instead of t for the thread id. Please see my post further down so that you can also have the ability to read the logic behind making these changes if you want.

[zeroibis]

OK I can see in the database that the correct out of date plugin is identified, now the issue is to find out why it does not display the correct plugin and instead displays a different one. Also I can see that the value for pluginid is not updated.

Ok so the issue is it records the thread id of the previous plugin in plugindb: it says the plugin is Weapon restriction but lists the thread id as being for the cheer plugin.

[zeroibis]

BAM FIXED!

dbplugins.php

Change line 127 to:

        $result = mysql_query( "INSERT INTO plugindb (pluginid,threadid,description,version) VALUES('$url[0]','$threadid','$description','$url[1]') ON DUPLICATE KEY UPDATE threadid='$threadid',description='$description',version='$url[1]'") or die(mysql_error());

The problem was that threadid='$threadid' was missing from the ON DUPLICATE KEY UPDATE part. There may be more glitches but I will need to test with more plugins to see if there is.

[zeroibis]

Crap I found a MAJOR problem that is due to the crazy way the sm forums work:

https://forums.alliedmods.net/showthread.php?p=522416 = cheer

https://forums.alliedmods.net/showthread.php?t=522416 = NOTHING

https://forums.alliedmods.net/showthread.php?t=105219 = Weapon restriction

https://forums.alliedmods.net/showthread.php?p=105219 = Page 4 of "Please, Translations Need for Advanced Team Attack Control" for amxmodx

OK so I have identified the issue:
If you use http://www.sourcemod.net/plugins.php to find the page it returns p= and if you use the forums to find the page via search it will return the t= location.

Which one do we want users to use p or t? Personally I would recommend P if this is the case as they can then use http://www.sourcemod.net/plugins.php to find their plugin and get