StatsLab12

[fhomess]

It has been a couple of weeks so it's time to have an updated version of StatsLab that will work with OOTP12. I haven't made any enhancements or improvements yet, and I haven't tested every page thoroughly. The read me is not updated either. Hence, this is officially version 0.0.1. When 1.0.0 comes out, there will be some enhancements and improvements.

NOTE: Links and web styles require that you use the full reports. I haven't done anything with the SQL reports upload yet.

In the meantime, this should work: StatsLab12.zip

One thing to note, the SQL configuration in OOTP12 has some additional options. The following should be checked:

• Insert DROP TABLE command
• Insert CREATE TABLE command
• Insert single quotes if empty
• Insert NULL if empty

The following SHOULD NOT be checked:

• Include field names in inserts

The following are optional:

• Replace accents - If you're having problems with accents, check this. Otherwise, leave it unchecked.
• Dump only cities in use - StatsLab doesn't currently use the cities table
• Dump only nations in use - StatsLab doesn't currently use the nations table

I'll update this post and thread when I've got more for all of you.

[Cooleyvol]

First in. Thanks, Frank!

[patriotcoach]

Anybody got this set up for an OOTP12 league yet?

Any problems so to speak?

[cody8200]

So far, so good. Working like a champ. Thanks for this Frank. You are awesome!

[almo]

Same install instructions that were used in 11? Is there anything different from an install perspective with regards to 12?

Thanks for any help I can get.

Soon to be new OOTP commish.

Almo

[cody8200]

The same instructions work just fine. At least they did for me. Good luck commish.

[cody8200]

Frank,

It seems the finance stuff is currently not working. I'm seeing this on the finance sheet.

Projected Payroll - StatsLab for OOTP12

[MikeyB]

I'm getting the following errors after installing, when logging in. Can anyone help?

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/ootpbml/public_html/StatsLab/login.php on line 151
Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/ootpbml/public_html/StatsLab/login.php on line 168

[hank9481]

Originally Posted by fhomess

One thing to note, the SQL configuration in OOTP12 has some additional options. The following should be checked:

• Insert DROP TABLE command
• Insert CREATE TABLE command
• Insert single quotes if empty
• Insert NULL if empty

The following SHOULD NOT be checked:

• Include field names in inserts

I can't explain why, but my version of OOTP 12 doesn't have these options available. Has anyone else encountered this?

EDIT: I now see why. It's a bug. I converted from OOTP X to OOTP 12. Obviously will need to be fixed.

[sdodd35@yahoo.com]

I too am getting these errors when logging in

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/mlob/public_html/StatsLab/login.php on line 151

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/mlob/public_html/StatsLab/login.php on line 168

Also, it will not save any of my contact information.. Just resets to blank boxes

[sdodd35@yahoo.com]

Originally Posted by sdodd35@yahoo.com

I too am getting these errors when logging in

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/mlob/public_html/StatsLab/login.php on line 151

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/mlob/public_html/StatsLab/login.php on line 168

Also, it will not save any of my contact information.. Just resets to blank boxes

Ok, I figured out a solution to the above errors... first create a backup of your current login.php that is currently on your server. Then replace it with the attached file. I have been testing it and it seems to be working correctly

[cody8200]

Originally Posted by hank9481

I can't explain why, but my version of OOTP 12 doesn't have these options available. Has anyone else encountered this?

EDIT: I now see why. It's a bug. I converted from OOTP X to OOTP 12. Obviously will need to be fixed.

I had this issue as well. It's because you ootp 11 import saves the sql config. files. The new options in 12 weren't on the old config files. Simply delete that config file and it will give you all of the options. I would tell you where that location is but I'm not on my home PC right now. Sorry.

[OpeningDay85]

Thank you Sdodd! First time user here and excited about it

[fhomess]

File updated with some minor fixes:
1. Login page will no longer cause errors and user info will save properly.
2. Coded around issues with #INF errors in SQL load.

[cody8200]

Contract screen:

Warning: mysql_num_fields(): supplied argument is not a valid MySQL result resource in /home/ootpbeli/public_html/StatsLab/payroll.php on line 102

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/ootpbeli/public_html/StatsLab/payroll.php on line 103

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/ootpbeli/public_html/StatsLab/payroll.php on line 178

Payroll (front office screen)

Warning: mysql_num_fields(): supplied argument is not a valid MySQL result resource in /home/ootpbeli/public_html/StatsLab/payroll.php on line 513

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/ootpbeli/public_html/StatsLab/payroll.php on line 514

Warning: arsort() expects parameter 1 to be array, null given in /home/ootpbeli/public_html/StatsLab/payroll.php on line 623

[fhomess]

Originally Posted by cody8200

Contract screen:

Warning: mysql_num_fields(): supplied argument is not a valid MySQL result resource in /home/ootpbeli/public_html/StatsLab/payroll.php on line 102

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/ootpbeli/public_html/StatsLab/payroll.php on line 103

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/ootpbeli/public_html/StatsLab/payroll.php on line 178

Payroll (front office screen)

Warning: mysql_num_fields(): supplied argument is not a valid MySQL result resource in /home/ootpbeli/public_html/StatsLab/payroll.php on line 513

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/ootpbeli/public_html/StatsLab/payroll.php on line 514

Warning: arsort() expects parameter 1 to be array, null given in /home/ootpbeli/public_html/StatsLab/payroll.php on line 623

Hmm... these are all related to the fact that the SQL dump no longer contains fields for whether or not the last year of a player contract is a team or player option. The contract extensions table does have these fields.

[cody8200]

Weird. The contract extension sql file is def. loaded. I just went back to the file load list to make sure.

[Tony M]

A quick question Frank. I have a universe with four major leagues - is there a way of not having StatsLab defaulting to one particular league.

[Cooleyvol]

Originally Posted by Tony M

A quick question Frank. I have a universe with four major leagues - is there a way of not having StatsLab defaulting to one particular league.

None that I know of.

I have three and installed three statslab apps with each set to default to its league.

[OpeningDay85]

1. When I try to load all the SQL Files through StatsLab I am able to load everything except the league_history_batting_stats.mysql.sql and players.mysql.sql files.

I get the following errors....


league_history_batting_stats.mysql.sql
Loading league_history_batting_stats.mysql.sql
insert into `league_history_batting_stats` VALUES (0, 0, 0, 0, 0, 0, 87032, 77965, 20783, 15309, 0, 0, 4131, 388, 2560, 1541, 542, 0, 10938, 7694, 0, 725, 0, 648, 0, 0, 2270, 0, 7079, 0, 0.2666, 0.3355, 0.4280, 11961.8121, 5.5329, 0.1614, 1.#INF, 0.7635, 73.9798, 0.0000, 0.0000); -> You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
insert into `league_history_batting_stats` VALUES (0, 0, 0, 0, 0, 0, 98393, 87884, 22741, 18282, 0, 0, 4606, 561, 2482, 1429, 591, 0, 11481, 8926, 0, 865, 0, 718, 0, 0, 2590, 0, 7649, 0, 0.2588, 0.3306, 0.4087, 12755.6118, 5.1827, 0.1499, 1.#INF, 0.7393, 70.7426, 0.0000, 0.0000); -> You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
insert into `league_history_batting_stats` VALUES (0, 0, 0, 0, 0, 0, 86187, 77467, 20131, 15214, 0, 0, 4016, 368, 2209, 1505, 540, 0, 10097, 7367, 0, 727, 0, 626, 0, 0, 2268, 0, 6593, 0, 0.2599, 0.3275, 0.4068, 11040.9813, 5.0957, 0.1469, 1.#INF, 0.7342, 73.5941, 0.0000, 0.0000); -> You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
insert into `league_history_batting_stats` VALUES (0, 0, 0, 0, 0, 0, 97794, 87886, 22423, 19092, 0, 0, 4470, 498, 2404, 1454, 589, 0, 11211, 8411, 0, 822, 0, 675, 0, 0, 2592, 0, 7372, 0, 0.2551, 0.3237, 0.3994, 12168.1925, 4.9237, 0.1443, 1.#INF, 0.7231, 71.1698, 0.0000, 0.0000); -> You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
... 282 queries executed

players.mysql.sql
... 42000 queries executed
insert into `players` VALUES (31388, 0, 0, "Lloyd", "Shunick\", "", 18, "1992-10-2", 81480, 206, 0, 220, 201, 0, 1, 100, 0, 0, 0, 0, -1, 23, 0, 0, 1, 1, 166, 104, 37, 29, 118, 72, "", "", 0, 0, 0, 0, 0, 0, 0, 0, 52, 51, 42, 63, 0, 0, 0, 0, 0, 0, 0, 0, 16, 1, 1, 3, 0, 0, 0, 0, 0, 1, 0, 100, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6, 0); -> You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '1992-10-2", 81480, 206, 0, 220, 201, 0, 1, 100, 0, 0, 0, 0, -1, 23, 0, 0, 1, 1, ' at line 1
... 42587 queries executed

2. I am trying to set up the draft ultity to no avil. We have already started the draft on our forums and so right now I need to manually enter our first 2 rounds through statslab. When selected manual pick, I am then needed to enter a player ID. When I do that, I get the following error

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/primetim/public_html/StatsLab/draftProcess.php on line 383
player not draft eligible


Any help or direction would be greatly appreciated. Thanks!