Quote:
Originally Posted by Alan T
I am getting the following when I try to update Development:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 2484 bytes) in /<DIR>/ootpsqlou/development.php on line 288
I run on a hosted (shared) server where I can not modify the php.ini to increase the memory size. Is this a bug, or just an issue with our online league running for more years than most online leagues?
|
I think the appropriate answer is "yes". There's numerous issues with the development tracker once leagues exceed a certain number of players. The fact that OOTP outputs ratings for retired players, the fact that it's necessary to join very large tables in SQL, and that every rating has to be translated to the league's ratings scales and then compared with the previous rating makes it an incredibly arduous task for the computer. I provided the ability to split out development by league so that you can run it in chunks, but I think there's still a point at which the code (as currently written) pukes.
Quote:
Originally Posted by DesertFox07
Frank,
I'm trying out V 11 on my local Vertrigo desktop server (running locally on Windows) and I can't get the Admin page to save my nav menu options (I want to turn on Career metrics, Last Sim, Awards, etc). When I check the database, I see you have two type of "install" values (4dmln which seems to be the default) and the my local file directory (which stats lab or MySQL is stripping the Window "\" character out of so my path never matches the value saved from the admin page). Any thoughts? Curious why the server path is used as a value for the install property as well.
|
To be honest, I haven't heard of anyone having success running StatsLab in a Windows environment and I haven't coded specifically for it. The problems that have arisen seem to be similar to the pathing issue you’ve got, but I haven’t taken the time to look into updating the code to see if I can fix it.
The server path is used to provide differenent settings for leagues that install multiple StatsLab instances for different leagues in their universe (e.g. MLB, NPL using the same MySQL database). Settings such as enabled pages are league specific, as you may want to enable All-Star voting in one instance and not another.
Quote:
Originally Posted by DesertFox07
Also, having used v9 and 10, the install process for 11 is a little convoluted now. Took me a few more tries to get everything up and running as opposed to StatsLabX.
|
Some of the differences avoid requiring write access to the server folders. In general, I’ve had far fewer questions about installation of StatsLab11 than StatsLabX. Some of that is probably that a lot of leagues were just converting over.