More work getting Views 2 handling working. Basic fields, filters, and arguments, including Date Browser arguments, are all working. Plugin display for the back/next Date Browser navigation is not yet added.

Temporarily adding in proposed Views patch for flexible date filters and arguments from #241759, to be removed if the patch gets into Views.

Get date popup working in node author section and fix validation and form_set_value code to work right in Drupal 6.

Simplify the API by assuming all date element values are handled in DATETIME format. The CCK Date module handles conversion of ISO and UNIX values to and from DATETIME values. This simplification of the core API should make it easier to get into core and makes the element handling easier to follow, plus I assume the first thing we'll do when a date API is in core is convert core timestamp fields to true DATETIME fields, so this would be the natural default.

Make allowances for special cases where the timezone is needed in a date conversion so that conversion to a timestamp doesn't get reset to the UTC value.

When date element is used as Views widget, the element validation gets skipped and the date doesn't get put back together correctly. Workaround this by checking for an array in $element['#value'].

#205208 Allow date ranges like -70:-18, for instance to limit date year to people who are 18 to 70 years old.

Turn off date part separators if the date parts use titles because the separators won't line up right in that case.

Make sure year range will expand to include the date's year even if it is outside the initial range.

Add themes to handle the spacing and puctuation between date and time and time parts in forms.

Rework handling of years back/forward to center on current year but also test to make sure it goes back far enough to pick up the current year in the value.

Standardize on date_make_date() instead of calling date_create() in some places so there is a central place to test the timezone and date values before creating the date.

Add method to customize the labeling of date parts to allow the label above the date part, inserted as the first item in the options array, or omitted.

Remove some functions that are not being used or move them so they are called only when needed to clean up the code.

Make am/pm element part back into select instead of radio so a blank value can be a valid option. Needed so date module can make intelligent substitutions of 'From' date values when 'To' date parts are left blank.

Fix a logic error in the way that blank values in the To date are overwritten by values in the From date when the date includes an am/pm selector.

Rework code so you can leave To date parts blank and have those parts automatically default to From date value. Change key for repeating multiple dates from 2 to 99 so we can add an option to set multiples to exactly 2 values as we will do in D6.

More reworking of the new API. Too many fixes to mention, but it is starting to feel fairly stable now.

Rework the logic for handling the date timezone and converting from and to the db storage timezone. Finally realized the widget cannot do the timezone transformation, the widget must always be handling a date in the same timezone so validation and other processes can work correctly no matter what route the form takes. It will be up to the field, not the element, to transform the date from gmt to the local timezone when the date is retrieved from storage and back again before saving it.

This is the first of a series of updates to get this change implemented. Things are likely to be buggy untill all these changes are reworked and committed.

Get the date repeat form working correctly and simplfy the repeat options to eliminate x day of year and x day of month to make the form less complex and easier for the user. Just getting the forms to display properly at this point. They don't yet function correctly.

Consolidate date elements into a single '#date_settings' array to not pollute the form. Add in a widget settings option to show the date repeat form on the node. The repeat form doesn't actually do anything yet!

Move override of site and user timezone setting into its own module so it can be turned on or off and removed once this is done by core. Also make PHP4 handling into a module instead of an include file so it can be turned on or off and removed once core no longer supports PHP4.

Reduce confustion by standardizing on use of 'month' instead of 'M' or 'mon', 'day' instead of 'D' or 'mday', etc, in granularity and date arrays.