partial_date 7.x-1.0-alpha6

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

Currently, the timestamp calculates these to be the same, although these are different. After these changes, the values will be 20110029 and 20110129, so the unknown month values will show before any values with known months.

Note: If it does not prove to hard, a helper module will be released at a latter date to fix entities, but for now, every entity needs to be edited and saved - without changing anything - to ensure that these fields become populated. Wait till alpha7 is released to ensure both changes are carried through.

Note that the timestamp column currently wildly inaccurate.

Note: timezone is used inconsistently and this will hopefully be fixed soon.