Bug #21466
closed
Deprecate serverTimezone
0%
Description
This setting is not used in the core and can be removed to prevent confusion.
(issue imported from #M12478)
Files
Updated by Andreas Kiessling over 13 years ago
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.
Updated by Alexander Opitz almost 11 years ago
- 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?
Updated by Simon Schaufelberger almost 11 years ago
Alexander, why do ask? Nothing has changed here. what do you mean with "more like you expect it"?
Updated by Alexander Opitz almost 11 years ago
- File 12748.diff 12748.diff added
Fix diff from Mantis import
Updated by Alexander Opitz almost 11 years ago
The serverTimeZone config is used on "date" fields, so the setting is used.
Updated by Simon Schaufelberger almost 11 years ago
as a side note: the place where this setting is missing is in fluid:
Updated by Oliver Hader over 10 years ago
- 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...
Updated by Oliver Hader over 10 years ago
- Status changed from Needs Feedback to Accepted
Updated by Stefan Neufeind over 9 years ago
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.
Updated by