Bug #52526

Unfinished programming of DateTime converter

Added by Stefan Froemken almost 2 years ago.

Status:New Start date:2013-10-04
Priority:Should have Due date:
Assigned To:- % Done:

0%
Category:-
Target version:2.0.1
Affected Flow version:Flow 2.0.0

Description

Hello Flow-Team,

it seems that there is an unfinished programming in TYPO3 Flow and fluid form handling.

My HTML for f:form:

<div class="extdiv">
    <label for="eventBegin"><f:translate key="tx_events2_domain_model_event.event_begin" /></label>
    <f:form.textfield id="eventBegin" property="eventBegin.date" />
    <f:form.hidden property="eventBegin.dateFormat" value="d.m.Y" />
    <f:form.hidden property="eventBegin.hour" value="0" />
    <f:form.hidden property="eventBegin.minute" value="0" />
    <f:form.hidden property="eventBegin.second" value="0" />
</div>

There is NO problem to create NEW entries with this form. This eventBegin-Array goes into DateTimeConverter and I get a valid DateTime-Object back.

BUT: When I edit this record, in my eventBegin-field stands: 2013-01-17 00:00:00+2

I don't have any possibility to format this date to d.m.Y

In ObjectAccess->getPropertyPath it gets the path "eventBegin.date". It executes getEventDate() and will then try to execute getDate() which isn't there if I return a string in my getEventBegin()-Method. If I return the original DateTimeValue it will return an unformattable Datestring as described above.

Stefan

Also available in: Atom PDF