Jump to:
| Project: | Date |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
| Issue tags: | rules integration |
Issue Summary
I'm putting this here because Date doesn't have rules integration itself and I suspect it is a CCK problem and not a Rules problem.
I've created a triggered rule that loads a user's Content Profile node on login and then executes a rule set. That rule set has a single rule with a single condition that check's the value of a date field in the Content Profile Node. When I select the date from the pop-ups in the condition and the save it the first time, it saves fine. When I go back to view the condition again, the year has had its first digit truncated (ie 1980 become 980) and the condition can not be re-saved as that value is an "illegal choice." I can re-set the year and re-save, but that doesn't fix it.
Comments
#1
In the same sequence as described here: http://drupal.org/node/409198
I tried using a condition that checked a calculated field and got this error:
warning: array_filter() [function.array-filter]: The first argument should be an array in /sites/default/modules/cck/includes/content.rules.inc on line 154.
warning: Invalid argument supplied for foreach() in /sites/default/modules/cck/includes/content.rules.inc on line 166.
#2
I can reproduce the problem, 2009 gets altered to 1009. However I don't see where the problem is, as the value is stored exactly and passed to content_field_form(). Is there some special handling in regards to the value of cck date fields?
@#1: Please open a separate issue and describe the exact steps to reproduce.
#3
Sounds similar to this: #411496: Exposed filter date query is '0009' not '2009' when using 'select' widget
Is this issue still valid? Could someone please test?
Thanks
#4
No followup after a few months of sitting at "postponed (maintainer needs more info)"