Bug #21466
closed
Hi Dmitry,
would you mind sending this to core list? I just stumbled upon this setting and also didn't find any place where it is used.
- Status changed from New to Needs Feedback
- Target version deleted (
0)
As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?
Alexander, why do ask? Nothing has changed here. what do you mean with "more like you expect it"?
Fix diff from Mantis import
- File deleted (
12748.diff)
The serverTimeZone config is used on "date" fields, so the setting is used.
- Assignee set to Oliver Hader
- Is Regression set to No
In TYPO3 CMS 6.2 the serverTimeZone is still present...
Working on issue #51918, I found this issue and agree that serverTimeZone does not make much sense...
- Target version set to 6.2.0
- Status changed from Needs Feedback to Accepted
Since 6.2 is out the door now, can we declare serverTimeZone (and maybe others) as deprecated officially and maybe not set it by default? It's not used in core, and that would give a clear signal that extensions should not rely on the setting.
- Status changed from Accepted to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by