Bug #53821
closed
Error with date/datetime fields and null evaluation
Added by Alexander Stehlik over 10 years ago.
Updated over 8 years ago.
Category:
Backend User Interface
Description
I just stumbled upon this (maybe it is a TYPO3 bug, than this issue can be closed):
When you use eval='null' together with date or time it is important, that the date / time is added after null:
eval='null,time'
If you add null at the end the fields will not be displayed as date / time but as integer values.
- Tracker changed from Task to Bug
- Project changed from 1369 to TYPO3 Core
Sorry for reacting belatedly, this was lost among other documentation issues. In my opinion this is a Core bug as there has never been any notion of precedence among the possible values of the "eval" property.
- Category set to Backend User Interface
- Target version set to next-patchlevel
- Is Regression set to No
- TYPO3 Version set to 6.2
- Subject changed from Improve documentation for input eval null to Error with date/datetime fields and null evaluation
- Target version changed from next-patchlevel to 7.4 (Backend)
- Target version changed from 7.4 (Backend) to 7.5
- Target version changed from 7.5 to 7 LTS
I could reproduce this on the current 6.2-branch, but not in 7-master (roughly 7.5.0 at this moment). Can somebody confirm it only affects 6.2 then?
- Status changed from New to Needs Feedback
Finally had the time to do some testing. I could not reproduce the issue any more in any current version (6.2, 7.6).
I nobody objects, issue can be closed :)
- Status changed from Needs Feedback to Closed
Closed on request of the reporter.
Thank you very much for your time and investigations.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by