[TYPO3-core] RFC: #12874: Tool>Log date fields does not work

Oliver Hader oliver at typo3.org
Tue Jan 19 16:21:28 CET 2010


Hi Steffen,

Am 19.01.10 14:48, schrieb Steffen Kamper:
> Hi olly,
> 
> Oliver Hader schrieb:
>>
>> As far as I can see, there is no bug (as also Benni pointed out).
>> Integrate the datepicker is a missing feature, however not a bugfix
>> for 4.3.
>>
> 
> i have a different point of view. For me it's a usability bug, because
> this part is simply not usable. Please read what the reporter writes,
> and i fully agree.
> 
>> Besides that, I'd like to see cleanups/formatting separated from
>> functional changes.
>>
> 
> i don't know how. I fixed the usability bug and (yes, this is added)
> instead of manual entry only i added datepicker too. But datepicker is
> not the central point of the patch, the input fields with reloading form
> is the problem.
> 
> Sure, this part of log module is not used by many users (maybe the
> reason why noone complaint until now). So imho with this patch the
> function is now usable and simply straight forward.
> Sure it's on you to decide where this go in.

Actually, Benni and me could not reproduce the mentioned bug in a plain
TYPO3 installation. Maybe other extensions/skins override the default
behaviour?

I'm going to review and test this patch and will post my votes
concerning 4.3 then. However, I still need some more information about
how to reproduce the behaviour.

One thing in the patch that I'm concerned about are the TYPO3_CONF_VAR
settings like ['SYS']['ddmmyy'] and the hardcoded order of the date
segents in the new parseDate() function.

olly
-- 
Oliver Hader
TYPO3 Release Manager 4.3


More information about the TYPO3-team-core mailing list