Last updated September 19, 2012. Created by arlinsandbulte on February 25, 2012.
Edited by cheese_monkey, arnoldbird, KarenS. Log in to edit this page.
Locale Settings
found at admin/config/regional/settings in Drupal 7.
Default time zone
Sets the default time zone for the website. Think of this setting as the time zone where the organization is based. When anonymous users visit the site, time fields displayed for them will be converted to this time zone.
User-configurable time zones
Determines if individual users can set their own default time zone. When the user is logged on, this effectively over-rides the above "Default time zone" setting.
First day of week:
Sets the desired first day of week. Mostly affects calendar grid displays, but also affects date-browser output when viewing dates by week. For most US/english sites, this should be set to Sunday. Monday is also frequently used in countries that follow the ISO 8601 date standard. Also, Saturday is common among Gulf Cooperation Council countries. (see http://en.wikipedia.org/wiki/Seven-day_week#Week_numbering for details)
Use ISO-8601 week numbers
For USA/Canada/Australia as well as many Middle East countries, week numbers DO NOT follow the ISO-8601 standard, and this option should be unchecked (unchecked is the default behavior).
To fully comply with the ISO-8601 standard for date & time, this option should be checked & First day of week should be set to Monday. This is common for much of Europe & Asia.
Time Zone settings unique to each date field instance
found at /admin/structure/types/manage/[machine_name_of_node-type]/fields/[machine_name_of_field]
Time zone handling
There are 5 different options for field Time zone handling:
- Site's time zone - When entering data into the field, the data entered is assumed to be in the site's time zone. When the data is saved to the database, it is converted to UTC. When retrieved from the database, the data is converted to the Site's time zone for anonymous users or the User's time zone for logged in users when User-configurable time zones is enabled.
- Date's time zone - With this option enabled, the date field adds a select box to explicitly specify the time zone for the date entered. When the date is saved to the database, it is not converted & the time zone information is saved with the date. When retrieved from the database, no conversion is performed and the date is displayed exactly as entered. [Actually, it appears some conversion is performed, but I don't know how to correct these docs because I'm not sure how the conversion is performed. See this issue.]
- User's time zone - When entering data into the field, the data entered is assumed to be in the user's time zone. When the data is saved to the database, it is converted to UTC. When retrieved from the database, the data is converted to the Site's time zone for annonymous users or the User's time zone for logged in users when User-configurable time zones is enabled.
- UTC - When entering data into the field, the data entered is assumed to be in UTC time zone. When the data is saved to the database, it is converted to UTC (e.g. no conversion necessary). When retrieved from the database, the data is converted to the Site's time zone for annonymous users or the User's time zone for logged in users when User-configurable time zones is enabled.
- No time zone conversion - The date entered is not converted when saved to the database. When retrieved from the database, the data is NOT converted and is displayed exactly as entered.
Comments
Change date mm-dd-yyyy to dd-mm-yyyy Date field - [solved]
I am adding an Events to a site in Drupal 7 with Date, Calender module and a few others.
When I looked at the Content Type (Events) I had created and wanted to fill in some test events I found that the Date filed showed the date in mm-dd-yyyy format - but I need dd-mm-yyyy.
So I went to http://www.example.com/admin/config/regional/date-time and changed the date settings to what I needed in long, medium and short.
But the date field in the Content Type (Events) did not change. I looked up and down www.drupal.org and the search engines to find an answer - but was not able to find what I was looking for.
So, I added some more date fields and they turned out correct.
Ergo, the answer is - once the date field has been set the at-that-time current date format is stored & "locked". Later date format changes will not effect those set earlier.
Solution - delete the field with the unwanted formatting and create a new date field under the correct date format setting.
Sure - if you have added data already to a site or if you realise that you need to make the changes on a life site you'll have a bid of a headache exporting nodes and re-formatting the dates before re-importing them into a new Content Type.
..........
-----------
Good luck .....
... more recent results of trying Drupal just once are -
www.native-power.de
Malls and More