Bug #22946
closed
Starttime/endtime default to 01-01-70 (-40 yrs) in list view
0%
Description
Elements in list view without an editor defined starttime or endtime set are saved to the db with value zero in cols starttime and endtime. Now I noticed that this zero finds its way to the backend if you display the according "set fields" resulting in the info that a default element (subpage, record ...) of the page started and ended 40 years ago. Well, while this is technically correct I propose to prioritize usability in this case and omit any time specification if no other value than zero is given ... besides it takes a whole lot of time to explain this to puzzled users ...
Install TYPO3, current version
Create a page
Put something in there
View in list module with set fields starttime and endtime
I can reproduce this issue with every version of 4.3 and 4.4. I checked 4.2 (have an old dummy project on 4.2.6) and did find any problems there.
datebase collations/connections utf-8
PHP internal/external charsets utf-8
(issue imported from #M14803)
Updated by
Updated by Benni Mack about 13 years ago
- Target version deleted (
0)
I think this is fixed with the latest maintenance releases. Can be closed...
Updated by Steffen Gebert about 13 years ago
- Status changed from New to Resolved