Bug #42414
closed
Scheduler frequency in cron style
0%
Description
I've noticed that Scheduler doesn't resolve correctly frequency in cron style.
First problem - an hour 1 hour.
Frequency "0 4 * * 0" (every sunday 4 am.) but next execution is scheduled at 2012-10-28 3:00 (Sunday 3 am.).
Second problem - day of week. I think there should be a warning during saving the taks.
Frequency "0 23 * * 7" where 7 is wrong, but is scheduled at 2012-10-28 22:00 (Sunday 10 pm.).
Noticed in TYPO3 4.5.19 and 4.6.12. Example on the image.
Files
Updated by Thorsten Kahler about 12 years ago
- Status changed from New to Needs Feedback
- Assignee set to Tomasz Krawczyk
Hi Tomasz,
Tomasz Krawczyk wrote:
First problem - an hour 1 hour.
Frequency "0 4 * * 0" (every sunday 4 am.) but next execution is scheduled at 2012-10-28 3:00 (Sunday 3 am.).
this rather seems like an issue with the switch from daylight savings time to normal time. Is the value still wrong?
Second problem - day of week. I think there should be a warning during saving the taks.
Frequency "0 23 * * 7" where 7 is wrong, but is scheduled at 2012-10-28 22:00 (Sunday 10 pm.).
"7" is an absolutely valid week day value in crontab.
Updated by Tomasz Krawczyk about 12 years ago
Hi Torsten,
I'm not sure if it is because of daylight savings. I'm from Poland and I use GMT+1 time zone.
According to http://en.wikipedia.org/wiki/Cron the fifth parameter should be 0-6. I have to admit somewhere in the classes I saw a comment that suggested using 1-7. Then 0 as a fifth parameter is incorrect but the extension allows using both 0 and 7.
Updated by Tomasz Krawczyk about 12 years ago
Thorsten,
My mistake the fifth parameter may be 0-7 but this one hour is strange to me.
Updated by Alexander Opitz over 11 years ago
Hi Tomasz,
what is the state of this issue, did something change with newer versions?
Updated by Tomasz Krawczyk over 11 years ago
Hi Alexander,
I didn't check newer T3 versions. I will check it on 27 October - when I'll change time CEST to CET.
Updated by Alexander Opitz about 11 years ago
- Is Regression set to No
We have it after 27. October, so did you test again?
Updated by Tomasz Krawczyk about 11 years ago
Currently I see no problem. I think the bug may be closed.
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Tomasz Krawczyk)