Project

General

Profile

Actions

Bug #19928

closed

Autocreation of records inserts wrong timestamps if user don't have access on that field

Added by Sven Weiss almost 16 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2009-01-28
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

I found this bug because I am beginning with workspaces and don't want that some persons edit the starttime or endtime of records. So I don't give them access to that field.
Now if the user is in his workspace and saves the record, the date and datetime fields get wrong value by autocreation of the new record because of "timezone" bug.

I completly debugged it and found the lines to changed:
class.t3lib_tcemain.php
function checkValue_input_Eval($value,$evalArray,$is_in) {
...
case 'date':
case 'datetime':
$value = intval($value);
if ($value>0 && !$this->dontProcessTransformations) {
$value -= date('Z', $value);
}
break;
...

Here the field gets timestamp-3600 seconds because the use of "date" function here I think is the wrong way.

(issue imported from #M10288)


Related issues 1 (0 open1 closed)

Has duplicate TYPO3 Core - Bug #20260: starttime eval date produces time-differences on same values!?ClosedChristian Kuhn2009-04-01

Actions
Actions

Also available in: Atom PDF