Bug #80679
closed
Input field eval datetime in FlexForm converts to wrong timestamp
Added by R3 H6 about 7 years ago.
Updated almost 7 years ago.
Category:
DataHandler aka TCEmain
Description
A input field with eval datetime converts to a wrong timestamp.
After saving a form, the date will have a difference of 2 or 4 hours (Summertime).
- Related to Bug #79957: TCA fields with eval types "time" or "timesec" decrease on every save added
- Related to Bug #79557: Date fields DataMapper handling problem added
- Related to Bug #79613: Saving wrong Date into DB if Field is of type DATE added
- Related to Bug #68651: Datetime() properties have wrong timezone added
- Related to Epic #80852: Datetime handling in backend added
I like to be more precise.
Eval set to datetime seems to work fine in FlexForm.
The problem is if eval is set to time, then the time changes with every saving.
As far as I could see the difference between datetime and time is, that in DataHandler::checkValue_input_Eval $value is an timestamp for time (1494418260), and a date string for datetime (2017-05-10T14:11:00+00:00).
Maybe the problem is somewhere in a JavaScript.
- Status changed from New to Accepted
- Parent task set to #77562
- Is Regression changed from No to Yes
- Status changed from Accepted to Closed
- Parent task deleted (
#77562)
Same issue as #79957. Closing as duplicate.
- Related to deleted (Bug #79957: TCA fields with eval types "time" or "timesec" decrease on every save)
- Is duplicate of Bug #79957: TCA fields with eval types "time" or "timesec" decrease on every save added
- Related to deleted (Epic #80852: Datetime handling in backend)
- Is duplicate of Bug #79249: TCA fields with eval types "time" or "timesec" are incorrectly stored in the database added
- Is duplicate of deleted (Bug #79957: TCA fields with eval types "time" or "timesec" decrease on every save)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by