-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2017 sql schedule going to be ready this year? #37
Comments
Hi, 3rd. Year as a happy and thankful user of your code with every year donation as well. |
May not be the best way to do this, but, after updating San Diego (SD -> LAC) and Rams (LA -> LAR) and making some other code and image (name) changes ... this is the SQL version of the 2017 schedule. (Again, you'll have to make the other changes, too, but this will work after that.) |
Thanks very much. I'm all set. |
Quick question. @bwdgraphics On this line |
I think that might be an error. I am actually using old code that I update each year, so mine does not have the week=2 part. It's just: $url = "http://www.nfl.com/ajax/scorestrip?season=".SEASON_YEAR."&seasonType=REG&week=".$week; It's quite possible that I noticed that at some point and changed it - but I have not kept any sort of records really for this code as it's just for fun. The above usually works for me. (It used to reference ESPN scores which were available anytime/always - NFL.com scores load well after the game is finished on occasion.) |
xSirThomasx, see the pull request link below for comments on how others have done this. I used most of numericOverflow's code in my fork. My fork also adds the option of hiding a users picks via a config option and tracking tiebreaker points. |
Everything is fine. I changed the year to 2017 and left the rest as I found it. |
Was just wondering if the 2017 sql file will be ready this year, or should we just create our own by hand based on the 17 week schedule? I did a donation :-)
The text was updated successfully, but these errors were encountered: