Bug #22329
closed
Date field in content elements
0%
Description
I'm not sure if this is a bug but it looks like one. TYPO3 ver. 4.3.2. When a date is entered in header section of some content element it shows up correctly in BE. However on a FE page it is displayed as 01.01.1970. I made an upgrade from 3.8.1 to 4.3.2 so maybe this is the couse for this?
(issue imported from #M13919)
Updated by Susanne Moog about 14 years ago
Hi, could you have a look at the definition of lib.stdheader.5 in your TypoScript template (with the object browser)? There the date reading and formatting is done.
I just tested with 4.3.3 and all works well.
Updated by Nino Katic about 14 years ago
Ok this is mine lib.stdheader.5:
field = date
if
isTrue
field = date
date = d/m Y
[strftime] = %x
[prefixComment] = 2 | Header date:
Updated by Ernesto Baschny over 13 years ago
The problem here is that you have date and strftime set. Both will be applied one after the other and thus you get bogus output.
The issue comes from your older TypoScript templates which probably contains something like this:
lib.stdheader.5.date = d.m.YIn the new CSC-template we have:
lib.stdheader.5.strftime = %xso having both is wrong.
Simply remove your lib.stdheader.5 from your TypoScript template, and let the new default do the rest (the "%x" makes the date locale dependent).
So I mark this issue as closed. Thanks!