server-status-project/server-status

V2 - Beta Issues

Tealk opened this issue · 1 comments

Tealk commented

Hello,

I have found the following errors in the beta.

Summary:

  • Correct variables
  • path to head.txt in admin
  • the overview of services is buggy
  • sorting the services are random
  • invalid endtime
  • sometimes the worst case is not displayed at the service group, multiple loading fixes the problem

Details

on the installation page I get the following errors:

Warning: Use of undefined constant SUBSCRIBE_EMAIL - assumed 'SUBSCRIBE_EMAIL' (this will throw an Error in a future version of PHP) in /var/www/vhosts/hosting106432.a2f1e.netcup.net/httpdocs/status_admin/template.php on line 31

Warning: Use of undefined constant SUBSCRIBE_EMAIL - assumed 'SUBSCRIBE_EMAIL' (this will throw an Error in a future version of PHP) in /var/www/vhosts/hosting106432.a2f1e.netcup.net/httpdocs/status_admin/template.php on line 40

Warning: Use of undefined constant SUBSCRIBE_TELEGRAM - assumed 'SUBSCRIBE_TELEGRAM' (this will throw an Error in a future version of PHP) in /var/www/vhosts/hosting106432.a2f1e.netcup.net/httpdocs/status_admin/template.php on line 43

Warning: Use of undefined constant TG_BOT_USERNAME - assumed 'TG_BOT_USERNAME' (this will throw an Error in a future version of PHP) in /var/www/vhosts/hosting106432.a2f1e.netcup.net/httpdocs/status_admin/template.php on line 44

Warning: fread() expects parameter 1 to be resource, null given in /var/www/vhosts/hosting106432.a2f1e.netcup.net/httpdocs/status_admin/template.php on line 62

When I go to /admin after installation I get:

Warning: fopen(head.txt): failed to open stream: file or directory not found in  /var/www/vhosts/hosting106432.a2f1e.netcup.net/httpdocs/status_admin/template.php on line 61
Unable to open head.txt!

It seems that the path is wrong, because when I copy the head.txt into the admin folder it works

The overview seems to be buggy and the service groups are not sorted like in the admin area.
CleanShot 2021-03-18 at 09 45 00

When creating a maintenance, the message "Error! End time is invalid!"
CleanShot 2021-03-18 at 10 02 43

worst case
CleanShot 2021-03-19 at 10 40 07

Tealk commented

invalid endtime seems to be a safari problem