Actions
Bug #79957
closedTCA fields with eval types "time" or "timesec" decrease on every save
Status:
Closed
Priority:
Must have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2017-02-22
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
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
Updated by Markus Sommer almost 8 years ago
- File TYPO3_CMS_Master__TYPO3_CMS_8_7_0-dev_.png TYPO3_CMS_Master__TYPO3_CMS_8_7_0-dev_.png added
- Priority changed from Should have to Must have
- Target version set to 8 LTS
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.
Updated by Markus Sommer almost 8 years ago
- Sprint Focus set to Stabilization Sprint
Updated by Christian Kuhn almost 8 years ago
- Target version deleted (
8 LTS) - Sprint Focus deleted (
Stabilization Sprint)
Updated by Mona Muzaffar almost 8 years ago
- Related to Bug #80679: Input field eval datetime in FlexForm converts to wrong timestamp added
Updated by Mona Muzaffar almost 8 years ago
- Related to Epic #80852: Datetime handling in backend added
Updated by Alex Kellner almost 8 years ago
This is still a critical thing in my eyes. Records with time fields are not usable since 8.6 any more :/
Updated by Markus Klein over 7 years ago
- Status changed from New to Accepted
- Parent task set to #77562
Updated by Markus Klein over 7 years ago
- Related to deleted (Bug #80679: Input field eval datetime in FlexForm converts to wrong timestamp)
Updated by Markus Klein over 7 years ago
- Has duplicate Bug #80679: Input field eval datetime in FlexForm converts to wrong timestamp added
Updated by Riccardo De Contardi over 7 years ago
- Related to deleted (Epic #80852: Datetime handling in backend)
Updated by Markus Klein over 7 years ago
- Status changed from Accepted to Closed
This solved with #79249.
Will mark this one as duplicate an close.
Updated by Markus Klein over 7 years ago
- Is duplicate of Bug #79249: TCA fields with eval types "time" or "timesec" are incorrectly stored in the database added
Updated by Markus Klein over 7 years ago
- Has duplicate deleted (Bug #80679: Input field eval datetime in FlexForm converts to wrong timestamp)
Actions