TYPO3 Core

That's probably because the field's value is 0 and timestamp 0 means beginning of unix time, which is 1.1.1970.

But the rendering should really be improved. Sven, could you investigate, where this output is rendered (and suppress the output, if value is 0 for date fields).

Perhaps the attached patch helps.
I identified 2 places:
1. date
2. datetime

Never used time oder timesec

Thanks for investigating, Sven!

Could you try the attached patch, please? Yours didn't apply for me. We don't have to set $l to a value in every case, it already has '' by default.

Could you also check this with 4.5beta3? Could not reproduce the problem there.

v2 works great for me with trunk.

We absolutely need this on in version 4.5

Hey guys.

What about fields with birthdays and a guy who happens to be born on Jan 1st, 1970 ? And what about birthdays where the date is negative (prior to 1970)?

Check out http://bugs.typo3.org/view.php?id=93 - same issue.

But for 01.01.1970 00:00, we don't show a value in TCEforms, but only in the list module.
Benni, would this patch also affect other places, where hiding the value might not be desired?

I checked also 4.3 (timestamp 0 is shown in List module) and 4.2, where it is NOT shown. So this behavior really has changed for 4.3

Can you remember the reason? I searched the ChangeLog for "date", but found only several daylight-saving-time issues.

I think this issue could be closed. I can not reproduce this in 6.2.2