Time zone is a locale parameter whose setting has an effect on the content of, for instance, the date field before any date is entered in it. The field shows a pseudo-placeholder text that changes according to the actual (user’s) time zone setting, compare:
For example, two different English-speaking editors, one working in London and the other in Berlin, want to use their local times. The Londoner prefers Greenwich Mean Time, while the Berliner prefers Central European Time.
In addition, the form of the time zone placeholder depends not only the time zone setting, but also on the language setting. If the preferred working language of the editor in Berlin were German rather than English, the placeholder could show _MEZ (abbrev. of Mitteleuropäische Zeit) instead of CET (abbrev. of Central European Time).
The default time zone of AdminCentral is set via the
getDefault method of the java.util.TimeZone class, which creates a time zone based on the time zone where the server is running.
You can change the way time zone is displayed in the UI. To do so, open the pull down menu in the top right corner of the browser window and click Edit user profile. In the Preferences tab, choose a timezone in the Time zone field:
The new time zone setting is applied the next time you log in into AdminCentral.
All content in Magnolia is stored in the default time zone. By changing the time zone in user profile you control how the default time zone is rendered in the UI.
The server uses the default time zone (the server time) to store the
dates you enter in date/time fields. Consider the following example with
a custom field called
myDate, which has the
time property set to
If both server and user time zones are set to CET (default, UTC+1) and in the period of the year which observes the daylight saving time you enter 2019-07-12 04:00 in the custom field, the value will be saved to JCR as follows:
However, if server time zone is CET but user time zone is PST (UTC-8), and you enter the same value (2019-07-12 04:00) in the field, Magnolia will not store the value as
but rather as a transcoded value seen from the server’s perspective, keeping the server’s UTC offset as the baseline: