Releases for Partial Date

partial_date 7.x-1.0-beta1

7.x-1.0-beta1

New features

Bug fixes

This release has a number of bug fixes and enhancements.

Limited field validation is now enforced.

1) If the field is marked as required, then you will get a validation error if there are no items with any values

#1536344: The required option doesn't work

2) Minimum component mix has been added. This allows you to select what components are required to make a partial date valid. For example, you can specify that the From and To years are required. During validation, a field that is not empty is then checked against these.

#1536348: Allow individual date parts to be required

An approximate component has been added

This adds a checkbox (if enabled) that allows users to mark the date as approximate.

A corresponding formatter option has been added that only shows if the date is flagged as approximate. This is applied to both from and to dates in the case of ranged date fields.

Inline ranged theming is now optional
This required overriding the core theme_form_element() [only for this widget], and rendering the date components in this. This is a configurable setting in the instance settings.

#1353400: Provide inline option for date widgets

Remove checkbox is now optional

partial_date 7.x-1.0-alpha6

7.x-1.0-alpha6

New features

Bug fixes

This release contains a number of minor bug fixes and enhancements.

Bug fixes

#1353332 - fix to two timezone notices on the widget form
#1353348 - fixed single value field widget labels (these were not showing)

Features

#1342642 - added time increment settings for minutes and seconds
Added standardized widget formatting of minutes and seconds to "00" to "59" (leading zeros)
Added two new year options: BC or BCE only displays. Years after 1BC are not suffixed with AD or CE for these values.
Added range separator option.

Data storage changes

Estimates are now used to pre-populate the corresponding components in the database. This will ensure that views will be able to use the main component columns even when only estimates are specified.

Alpha7 should see the timestamp column changed so that this will truly represent the stored data via the following algorithm.

timestamp = float_from_string(year + (month ? zp(month) : 00) + (day ? zp(day) : 00) + (hour ? zp(hour + 1) : 00) +  (minute ? zp(minute + 1) : 00) +  (second ? zp(second + 1) : 00));

function zp(value) {
  return zero_pad(value, 2)
}

This will allow better sorting of the values. For example: 2011-unknown-29 and 2011-01-29

partial_date 7.x-1.0-alpha5

7.x-1.0-alpha5

New features

Bug fixes

There is no upgrade path from 7.x-1.0-alpha3 as the field schema has changed significantly.

This is a totally refactored version. It should be still considered as a early alpha, although basic functionality should throw minimal notices and store date & time components / estimates without issue. The timestamps (automatically generated from the date components) are not currently working, so any content created will have to be re-saved at a latter date to update these errors.

Please test, clearly report any issues and help push this into a stable production ready module