Bug #79957
closed
TCA fields with eval types "time" or "timesec" decrease on every save
Added by Thomas Kieslich about 7 years ago.
Updated almost 7 years ago.
Category:
FormEngine aka TCEforms
Description
A TCA Column with this config
'config' => [
'type' => 'input',
'size' => '12',
'eval' => 'time',
'default' => '0'
]
decrease on first save for 2 hours and on every next save for on hour.
Tested on Mamp Pro on osx with CET Timezone. Php date.timezone is Europe/Berlin.
Files
Hallo,
The Problem is reproducible with ext:styleguide
Tested with the "elements basic"
After each save the value reduced by 1 to 4 hours.
This behavior is only by the "inputdatetime_5 eval=time" and the "inputdatetime_6 eval=timesec" field.
I think it commes from the timepicker.
- Sprint Focus set to Stabilization Sprint
- Target version deleted (
8 LTS)
- Sprint Focus deleted (
Stabilization Sprint)
- Related to Bug #80679: Input field eval datetime in FlexForm converts to wrong timestamp added
- Related to Epic #80852: Datetime handling in backend added
This is still a critical thing in my eyes. Records with time fields are not usable since 8.6 any more :/
- Status changed from New to Accepted
- Parent task set to #77562
- Related to deleted (Bug #80679: Input field eval datetime in FlexForm converts to wrong timestamp)
- Has duplicate Bug #80679: Input field eval datetime in FlexForm converts to wrong timestamp added
- Related to deleted (Epic #80852: Datetime handling in backend)
- Status changed from Accepted to Closed
This solved with #79249.
Will mark this one as duplicate an close.
- Is duplicate of Bug #79249: TCA fields with eval types "time" or "timesec" are incorrectly stored in the database added
- Has duplicate deleted (Bug #80679: Input field eval datetime in FlexForm converts to wrong timestamp)
- Parent task deleted (
#77562)
Also available in: Atom
PDF