Page 1 of 1

Version 3.10

Posted: Sat Oct 12, 2024 2:18 pm
by Panther
UTStatsDB is back, with updates to make it compatible with PHP 8 (including 8.2), plus various bug fixes and enhancements to the special event tracking. It's been tested a bit with MySQL, but I still need to test with Microsoft SQL and SQLite. One downside with this release is that I've not completed an update routine to automatically update databases from earlier versions, but I have doubts as to whether anyone still has an active system running version 3.06. You can see the demo page running with UT '99, 2004, and UT3:
https://utstatsdb.com/demo/

Once I finish testing and making any corrections that might be needed for SQLite and Microsoft SQL, I'll post the new version.

Re: Version 3.10

Posted: Sun Oct 20, 2024 5:35 am
by robbo987
Having some problems with is while running openlitespeed and MariaDB php version 8.3 (cyberpanel)

To start with all i would get is 500 errors. until i renamed the statsdb.inc-sample file to statsdb.inc. i then edited the info in manually but now all i receive is "Database type error"

If i go to /admin.php i get Database type error - you must set $dbtype in your statsdb.inc.php file. even though it is already set to database type "MySQL"

is there a certain type for MariaDB? or is this an openlitespeed problem?

Re: Version 3.10

Posted: Mon Oct 21, 2024 11:16 pm
by Panther
I started going through the documentation a bit more after I released this and I noticed that I failed to specify that the MySQL type is now "MySQLi" since the old database format is no longer supported in PHP. Setting it to MySQLi should resolve the issue for you.

Re: Version 3.10

Posted: Mon Oct 21, 2024 11:27 pm
by Panther
The next version will include a check for the file with a friendly message instead of generating a critical error.

Re: Version 3.10

Posted: Mon Dec 23, 2024 8:59 pm
by Panther
I've found a couple of issues in this release. One is a typo in the logs.php file that affects command-line stat parsing.
To fix this, just change:

Code: Select all

if ($setglobals = true) {
to:

Code: Select all

if ($setglobals == true) {

The other involves UTF-8 encoding, affecting things such as map names and author names. I will fix this in the next release.