Log of /contributions/modules/date/date_api_elements.inc
Parent Directory
| 
Revision Log
| 
Revision Graph
Revision
1.49.2.1.2.28
Fri Sep 5 11:03:56 2008 UTC
(14 months, 3 weeks ago)
by
karens
Branch:
DRUPAL-6--2
Changes since
1.49.2.1.2.27: +1 -1 lines
FILE REMOVED
Update to new Views2 API. Now requires latest versions of Views and CCK, and files have been re-arranged.
Revision
1.49.2.1.2.25 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Aug 25 09:22:07 2008 UTC
(15 months ago)
by
karens
Branch:
DRUPAL-6--2
Changes since
1.49.2.1.2.24: +73 -38 lines
Diff to
previous 1.49.2.1.2.24
, to
branch point 1.49.2.1
#275919, #267195 Clean up date_select validation:
add field name to from and to date so the name can be used in error messages,
combine error messages for field parts into a single message,
remove #options from text elements so we don't get meaningless core message about an invalid option,
set error on whole element so error fields will get outlined.
Revision
1.27.2.38 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Aug 25 09:21:44 2008 UTC
(15 months ago)
by
karens
Branch:
DRUPAL-5--2
Changes since
1.27.2.37: +79 -41 lines
Diff to
previous 1.27.2.37
, to
branch point 1.27
#275919, #267195 Clean up date_select validation:
add field name to from and to date so the name can be used in error messages,
combine error messages for field parts into a single message,
remove #options from text elements so we don't get meaningless core message about an invalid option,
set error on whole element so error fields will get outlined.
Revision
1.49.2.1.2.22 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Aug 19 13:39:22 2008 UTC
(15 months, 1 week ago)
by
karens
Branch:
DRUPAL-6--2
Changes since
1.49.2.1.2.21: +14 -8 lines
Diff to
previous 1.49.2.1.2.21
, to
branch point 1.49.2.1
#292617 Make sure the Date Repeat form works properly wth all possible date widgets,
#273656 Make the Date Repeat form use the same widget the regular date form uses.
This is the beginning of the fixes needed, there may be more fixes coming.
Revision
1.44 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Apr 10 01:08:28 2008 UTC
(19 months, 2 weeks ago)
by
karens
Branch:
MAIN
Changes since
1.43: +6 -2 lines
Diff to
previous 1.43
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.
Revision
1.39 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Feb 19 15:37:59 2008 UTC
(21 months, 1 week ago)
by
karens
Branch:
MAIN
Changes since
1.38: +11 -11 lines
Diff to
previous 1.38
Get date popup working in node author section and fix validation and form_set_value code to work right in Drupal 6.
Revision
1.36 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Feb 17 14:01:39 2008 UTC
(21 months, 1 week ago)
by
karens
Branch:
MAIN
Changes since
1.35: +9 -16 lines
Diff to
previous 1.35
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.
Revision
1.27.2.9 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Feb 17 13:59:00 2008 UTC
(21 months, 1 week ago)
by
karens
Branch:
DRUPAL-5--2
Changes since
1.27.2.8: +9 -16 lines
Diff to
previous 1.27.2.8
, to
branch point 1.27
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.
Revision
1.35 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sat Feb 16 19:32:47 2008 UTC
(21 months, 1 week ago)
by
karens
Branch:
MAIN
Changes since
1.34: +4 -2 lines
Diff to
previous 1.34
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.
Revision
1.33 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Feb 15 22:56:34 2008 UTC
(21 months, 1 week ago)
by
karens
Branch:
MAIN
Changes since
1.32: +18 -2 lines
Diff to
previous 1.32
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'].
Revision
1.32 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Feb 15 13:23:53 2008 UTC
(21 months, 1 week ago)
by
karens
Branch:
MAIN
Changes since
1.31: +1 -1 lines
Diff to
previous 1.31
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.
Revision
1.27.2.4 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Feb 15 13:01:19 2008 UTC
(21 months, 1 week ago)
by
karens
Branch:
DRUPAL-5--2
Changes since
1.27.2.3: +2 -2 lines
Diff to
previous 1.27.2.3
, to
branch point 1.27
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.
More commits are coming to re-apply patches made after this change.
Revision
1.26 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Jan 4 15:26:09 2008 UTC
(22 months, 3 weeks ago)
by
karens
Branch:
MAIN
Changes since
1.25: +8 -4 lines
Diff to
previous 1.25
#205208 Allow date ranges like -70:-18, for instance to limit date year to people who are 18 to 70 years old.
Revision
1.25 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Jan 4 14:00:24 2008 UTC
(22 months, 3 weeks ago)
by
karens
Branch:
MAIN
Changes since
1.24: +13 -3 lines
Diff to
previous 1.24
Turn off date part separators if the date parts use titles because the separators won't line up right in that case.
Revision
1.24 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Jan 4 13:11:32 2008 UTC
(22 months, 3 weeks ago)
by
karens
Branch:
MAIN
Changes since
1.23: +22 -9 lines
Diff to
previous 1.23
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.
Revision
1.23 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Jan 2 18:25:57 2008 UTC
(22 months, 3 weeks ago)
by
karens
Branch:
MAIN
Changes since
1.22: +11 -4 lines
Diff to
previous 1.22
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.
Revision
1.22 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Jan 2 17:01:57 2008 UTC
(22 months, 3 weeks ago)
by
karens
Branch:
MAIN
Changes since
1.21: +51 -16 lines
Diff to
previous 1.21
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.
Revision
1.20 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Dec 31 12:04:12 2007 UTC
(22 months, 4 weeks ago)
by
karens
Branch:
MAIN
Changes since
1.19: +4 -3 lines
Diff to
previous 1.19
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.
Revision
1.17 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Dec 18 11:49:16 2007 UTC
(23 months, 1 week ago)
by
karens
Branch:
MAIN
Changes since
1.16: +2 -2 lines
Diff to
previous 1.16
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.
Revision
1.14 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Dec 14 16:19:11 2007 UTC
(23 months, 2 weeks ago)
by
karens
Branch:
MAIN
Changes since
1.13: +46 -28 lines
Diff to
previous 1.13
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.
Revision
1.13 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Dec 13 21:36:47 2007 UTC
(23 months, 2 weeks ago)
by
karens
Branch:
MAIN
Changes since
1.12: +120 -75 lines
Diff to
previous 1.12
More reworking of the new API. Too many fixes to mention, but it is starting to feel fairly stable now.
Revision
1.12 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Dec 5 18:00:54 2007 UTC
(23 months, 3 weeks ago)
by
karens
Branch:
MAIN
Changes since
1.11: +103 -238 lines
Diff to
previous 1.11
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.
Revision
1.10 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sat Oct 27 12:45:19 2007 UTC
(2 years, 1 month ago)
by
karens
Branch:
MAIN
Changes since
1.9: +4 -9 lines
Diff to
previous 1.9
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.
Revision
1.9 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Oct 26 21:56:55 2007 UTC
(2 years, 1 month ago)
by
karens
Branch:
MAIN
Changes since
1.8: +70 -59 lines
Diff to
previous 1.8
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!
Revision
1.7 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Oct 1 00:03:36 2007 UTC
(2 years, 1 month ago)
by
karens
Branch:
MAIN
Changes since
1.6: +3 -3 lines
Diff to
previous 1.6
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.
Revision
1.6 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Sep 25 14:16:04 2007 UTC
(2 years, 2 months ago)
by
karens
Branch:
MAIN
Changes since
1.5: +43 -45 lines
Diff to
previous 1.5
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.
Revision
1.4 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Sep 10 11:22:04 2007 UTC
(2 years, 2 months ago)
by
karens
Branch:
MAIN
Changes since
1.3: +14 -6 lines
Diff to
previous 1.3
Clean up date_popup and date_repeat. Date_popup is now functional, date_repeat is not yet. Add changes to date.install to match what was committed to the D5 branch.
Revision
1.2 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sat Sep 8 12:31:11 2007 UTC
(2 years, 2 months ago)
by
karens
Branch:
MAIN
Changes since
1.1: +66 -32 lines
Diff to
previous 1.1
Add in option to set different default values for the from and to dates so you can have something like the current date as the from date and one month from now as the to date, move the titles of the date_select sup-parts (year, month, day, etc) to a theme for easier overrides
Revision
1.1 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Sep 7 18:58:04 2007 UTC
(2 years, 2 months ago)
by
karens
Branch:
MAIN
Split elements between re-usable ones and cck-specific ones, rename some files, change element handling to match the way things will work in the D6 version of CCK to make porting easier, lots of small fixes from testing and debugging.
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.
