Skip to content

Release 1.2.4

Compare
Choose a tag to compare
@Newcomer1989 Newcomer1989 released this 12 Feb 05:35
· 116 commits to master since this release

! changed parameter 'check' for the worker.php (startscript). Now this parameter will only start the Ranksystem, if it was crashed. In case the Ranksystem was stopped with 'stop' parameter, it will not start the Ranksystem with 'check' parameter.
! you need to define a verification channel ID to the webinterface -> core; the needed channel has to be set up manually on your TS3 server; for more information read also the online help inside the webinterface at this parameter
* increased performance: on bigger databases it will run much faster (valuable on response speed of chat commands). on smaller databases it will reduce needed resources (CPU)
* improved memory handling (RAM)
* optimized session handling on stats page and webinterface; now the Ranksystem don't touch other sessions from the same domain (relevant to multiple Ranksystem installations or other systems on the same domain, which are also using sessions)
* optimized logs preview on webinterface (site load is much faster; now all lines will be shown, also array outputs on SQL errors; error and critical entries are now red colored)
* send a little more information about Ranksystem instance to ts-n.net like total_user, user_week_ total_online_week [..] (will be sent on update check; normally 2 times a day); there will not be sending any personal data of any user, it is only instance information! also, this information will never be shared without your agreement with third ones or published to be able to associate it with your instance; our plan is to build a summary of stats (of all instances) and perhaps we will share this sometime on a website
+ made the field "admin ID" multiple (unique client ID of the admin of the Ranksystem); multiple admin uuids can be entered comma separated; note that other admins are also be able to reset the password for the webinterface
+ added new chat command "!clean" to the Ranksystem Bot; the cleaning will run at least once a day; with this command you can force to make it instant
+ added a link to the verification process with that it is possible to redeem the token automatically (before it must be entered manually)
+ added new verification step, when the users IP between website and TS3 server differs; at this point the user can register himself also with a token; to protect from spams the user need to join a verification channel, where he will be able to choose himself to be able to receive the token
+ added a few more cleaning checks; now old avatars of deleted users will be deleted from the web space
+ added percentage column for lists of nations, platforms and versions
+ added update notification on stats page and webinterface, when an update was done the last few days ago; appears once a time per browser session
+ added new validation check on TS3 host address to prevent entering a port inside, which would be wrong placed here
+ added new validation check on defined servergroup IDs (rankup definition, servergroup exception, boost); the check will be done at 3 points:

  1. saving a wrong ID inside the webinterface
  2. on starting the Ranksystem Bot
  3. on the Bots job to update the servergroups, when one group gotten removed

+ added check when removing the server icon on the TS3 server; then it will now also remove the icon from the Ranksystem
+ added check when removing an icon of a servergroup on the TS3 server; then it will now also remove the icon from the Ranksystem
+ added check for slow running Ranksystem instance and offer suggestions to optimize the environment
+ added check to top user sites of the week and month; if there are not enough data collected, on this sites will be shown the message "not enough data..." instead of wrong results
- fixed wrong sorting of the column 'next servergroup' on List Rankup (stats page)
- fixed the nations list; full name wasn't showing for some languages, even though they were available
- fixed link to the webinterface on the stats page (and vice versa), which was not working when the website port was not default (80 or 443)