MHSanaei b124af2a1b fix(settings): accept five-field crontab for report and LDAP schedules ...

The panel scheduler runs WithSeconds(), whose parser rejects a standard
five-field crontab such as "30 8 * * *". An admin who typed one into the
Telegram/Discord notify time or the LDAP sync schedule saved it without
error, AddJob then failed at startup, and the job silently never ran.

Admin-typed schedules now go through internal/util/cronspec, which takes
an optional seconds column plus the @descriptors and hands the scheduler
a parsed cron.Schedule. CheckValid rejects an unparseable schedule on
save, and a stored legacy value falls back to the job's default instead
of dropping the job.

2026-10-11 20:37:04 +02:00

..

check_valid_test.go

fix(settings): accept five-field crontab for report and LDAP schedules

2026-10-11 20:37:04 +02:00

entity.go

fix(settings): accept five-field crontab for report and LDAP schedules

2026-10-11 20:37:04 +02:00

path_validation_test.go

refactor: focused service files, leaf subpackages, and an internal/ layout (#5167)

2026-06-10 15:19:22 +02:00