Describe the bug
When I make the default domain mycustomer.server.hoster.tld an alias of my-customer.de, the nightly traffic cronjob produces the following PHP notice:
PHP Notice: Undefined offset: 6 in /var/www/html/froxlor/lib/Froxlor/Cron/Traffic/TrafficCron.php on line 168
The warning points to this line. I queried the database to find the customer whose standard subdomain has ID 6 and queried the subdomains:
Note that there's no subdomain with ID 6. However, in the Froxlor domain list, there's the additional domain mycustomer.server.hoster.tld, which is not returned by the query above. This domain is marked as an alias of domain my-customer.de. When I remove the alias (i.e., set it to "no alias"), then the query above also returns the domain with ID 6:
Expected behavior
The traffic cronjob should work without warnings with any alias setting, or it should not allow configurations which result in warnings.
Additional context
The alias setting for the standard domain was enabled for a long time on this server., but this warning started to appear after Froxlor was updated from 2.1.2-1 to 2.1.3-1.
Describe the bug When I make the default domain
mycustomer.server.hoster.tld
an alias ofmy-customer.de
, the nightly traffic cronjob produces the following PHP notice:The warning points to this line. I queried the database to find the customer whose standard subdomain has ID 6 and queried the subdomains:
Note that there's no subdomain with ID 6. However, in the Froxlor domain list, there's the additional domain
mycustomer.server.hoster.tld
, which is not returned by the query above. This domain is marked as an alias of domainmy-customer.de
. When I remove the alias (i.e., set it to "no alias"), then the query above also returns the domain with ID 6:System information
Expected behavior The traffic cronjob should work without warnings with any alias setting, or it should not allow configurations which result in warnings.
Additional context The alias setting for the standard domain was enabled for a long time on this server., but this warning started to appear after Froxlor was updated from 2.1.2-1 to 2.1.3-1.