Project

General

Profile

Actions
Copy link

Bug #19855

closed

datetime evaluation again buggy in TYPO3 4.2.4-dev

Added by Jochen Rieger over 15 years ago. Updated over 5 years ago.

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

0%

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

Description

This is a bug report for TYPO3 4.2.4-dev

I know there has been a lot of discussion and fixes around the timezone problems. According to bugtracker entries and mailing list discussions the issue seemed solved to me.

But I just could reproduce the following:

1) Using 4.2.3: everything works as expected
2) Using 4.2.4-dev: Problem when entering future date that is after a daylight saving time change (in my case after saving: -2 hours)

(issue imported from #M10186)

Related issues 3 (0 open — 3 closed)

Related to TYPO3 Core - Bug #18977: Date/time field problem with timezone shifting when using the "+xx" and "d" syntaxesClosedErnesto Baschny2008-06-18

Actions
Related to TYPO3 Core - Bug #18474: Timezone BugClosedErnesto Baschny2008-03-18

Actions
Related to TYPO3 Core - Bug #20088: In BE time and datetime fields GMT-0 will be shown by javascript, but GMT+1 will be savedRejectedErnesto Baschny2009-02-24

Actions
Actions
Copy link
 #1

Updated by Jochen Rieger over 15 years ago

FYI: The described behaviour occurs with AND without the extension date2cal installed.

Actions
Copy link
 #2

Updated by Ernesto Baschny over 15 years ago

I was able to reproduce the problem. Will try to find a fix ASAP.

Actions
Copy link
 #3

Updated by Ingmar Schlecht over 15 years ago

Committed to the 4.2 branch.

Actions
Copy link
 #4

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF