[TYPO3-core] RFC #12358: BE-user last-login field uses "date" instead of "datetime"

Martin Kutschker masi-no at spam-typo3.org
Tue Oct 27 11:02:01 CET 2009


Steffen Kamper schrieb:
> Hi,
> 
> Martin Kutschker schrieb:
>> Steffen Gebert schrieb:
>>> Hi,
>>>
>>> This is SVN patch request.
>>>
>>> Type: Bugfix / no-brainer / follow-up to #6131
>>>
>>> Bugtracker references:
>>> http://bugs.typo3.org/view.php?id=12358
>>>
>>> Branches: trunk
>>>
>>> Problem:
>>> #6131 added a field with the Last login date of a BE-user as read-only
>>> field to TCEforms.
>>> Unfortunately, only "date" instead of "datetime" is set as eval-type.
>>> We have more detailed information (time!) - why don't we show that?
>>>
>>> Solution:
>>> Set eval to datetime
>>
>> +1 on reading
>>
> 
> +1 from my side too
> 
>>> Note:
>>> This is the same as for Start/Stop dates in access register.. there's no
>>> reason, to use only date.. don't know, why some devs nevertheless choose
>>> date.
>>
>> Using start/stop times (and not dates) requires a check on every page
>> hit. Currently TYPO3 delivers
>> the page from cache without that check (only access restrictions are
>> checked). That's the reason for
>> clear-cache-at-midnight config.
>>
> 
> you can set cache interval for page shorter than one hour so date/time
> would make sense.

Yes. But then you must make sure yourself that the cache for those pages are cleared often enough
that start/stop in hours (are minutes also needed) make the desired effect.

> It's read only when not coming from cache,

That's what I've written :)

Masi


More information about the TYPO3-team-core mailing list