Issue #1216878, Re-introduce 'repeat' as a field setting rather than a widget type so people can't try to switch back and forth between repeating and non-repeating dates. Eliminate repeat widgets.

Issue #1234140 by arlinsundbulte, Change terminology in user-facing text from 'From/To Date' to 'Start/End Date'.

Get rid of overlapping formatter functionality. There should be a default formatter with the option to choose a date format as a setting, not a formatter for each format. This was a leftover from the D6 functionality.

Re-organize all the field hooks into a single file and add the formatter settings form and summary. This will probably see more changes, this is a first pass.

Removing D6 updates, with all the D7 changes they won't make any sense in D7, formats and timezones are now in core, fields are different, etc.

More work on the upgrade path to be sure all the necessary modules get enabled and that date_popup formats get adjusted to formats that work with that module.

Make sure new required modules get enabled during the update, should have made the module list an array.

Remove database timezone handling by rolling back to previous version that used offsets instead. Based on problems noted in #218479 and #220663, we cannot count on database timezone handling to be available in MYSQL or work consistently with the timezone names that PHP uses in POSTGRES, so trying to do timezone conversions in the database is not going to work.

Synch with D5.2 version.

#218479 Add more information about db timezone support to the INSTALL.txt file and move the requirements test to the Date Timezone module.

Getting rid of offsets!! Alter query code to cast ISO and UNIX dates to native datetimes and do timezone conversion in the database. Much faster and more accurate.

This will mean this version of the code will not work for databases that are not able to do native timezone conversion, but even inexpensive shared hosts will probably have the MYSQL database timezone tables installed, and PostgreSQL has good timezone handling enabled by default.

The MYSQL timezone conversion code should be accurate, the PostgreSQL code looks right from the documentation but needs to be verified.

The offset fields can now be dropped from the Date fields since we only need the timezone name to do the conversion.

I probably missed some places that need to be adjusted for this change, but this should get most of the necessary fixes in place.

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.

Add conversion functions for iCal date, more cleanup of date_repeat and add a warning in the date_repeat info file that it is not ready to use yet.

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.