Actions
Bug #101254
closedDate field validated as incorrect when range.lower is set and setting a date in the future
Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Backend JavaScript
Target version:
-
Start date:
2023-07-05
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
Complexity:
Is Regression:
Yes
Sprint Focus:
Description
For example the styleguide field
'inputdatetime_11' => [
'label' => 'inputdatetime_11',
'description' => 'eval=datetime, default=0, range.lower=1627208536',
'config' => [
'type' => 'datetime',
'format' => 'date',
'default' => 0,
'range' => [
'lower' => 1627208536,
],
],
],
Try to set any date. The field can't be saved. FormEngine validation complains the value is incorrect.
Does not happen in TYPO3 v11.
Files
Updated by Nikita Hovratov over 1 year ago
- File date-invalid.png date-invalid.png added
- Description updated (diff)
Updated by Georg Tiefenbrunn about 1 year ago
- Related to Bug #102070: Validation and UX errors on TCA type=datetime when using range property added
Updated by Xavier Perseguers 2 months ago
- Priority changed from Should have to Must have
- TYPO3 Version changed from 13 to 12
- Is Regression set to Yes
I can reproduce this with TYPO3 v12. Does not happen in TYPO3 v11.
I have the feeling this is unrelated to a date in the future, validation just fails as soon as a "lower" range is configured.
Updated by Benjamin Franzke 15 days ago
- Status changed from New to Closed
Thanks for the Report!
We didn't see it while we encountered the same issue, it has been fixed in the meantime with: https://forge.typo3.org/issues/105430
Updated by Benjamin Franzke 15 days ago
- Is duplicate of Bug #105430: Date validation in FormEngine broken added
Actions