Bug #4474
closed
wording is not very good
100%
Description
I am just testing the ext and there is a problem with wording if a user forgets to set an interval.
error message: "Please insert a valid interval (> 0)"
but the label of the field is "Frequency (seconds or cron command)" > the word 'interval' is never mentioned, so IMO it would be the best to change the label to "Interval (seconds or cron command)" or the error msg.
Updated by Francois Suter about 15 years ago
- Status changed from New to Accepted
- Assignee set to Francois Suter
Just to explain the history of that difference: Gabriel actually has 2 different fields, plus a selector to choose between the type of input for the frequency (interval or cron command). I made all that transparent to the user, but still kept tests where I tried to guess which type of input was given and produce differentiated error messages.
But I agree that this may not help so much and will propose a different wording.
Updated by Francois Suter about 15 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Here's what I changed: I merged the invalid interval and invalid cron in a single message, which says: "Invalid frequency. Please enter either a number of seconds or a valid cron command." I hope this is fine.
Done in r1203
Updated by
Updated by Francois Suter over 12 years ago
- Status changed from Resolved to Closed
Updated by Michael Stucki almost 11 years ago
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler