Closed (won't fix)
Project:
Date
Version:
6.x-2.4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Apr 2010 at 16:02 UTC
Updated:
26 Oct 2018 at 03:03 UTC
Jump to comment: Most recent
The problem that is happening is that somehow when a "conditional" date field is unset that field's value does not properly get stored in the database.
This problem can be observed in the file: date/date_token.inc on line 39:
$item['value'] = trim($item['value']);
$item['value'] ends up being set to array('date' =>)
Here, trim function does not expect an array() to be passed to it.
If I were to set the appropriate condition so that I can edit the date field, then the resulting $item['value'] is not an array.
Therefore, this only happens when the date field is disabled (and possibly when hidden) by a conditional field.
Comments
Comment #1
thekevinday commentedThis bug seems to vanish with the 2.x-dev version of conditional fields.
Once I spend enough time to confirm that this is the case, then I will close this bug report given that this problem now appears to be more of a conditional fields issue than a date issue.
Comment #2
damienmckennaUnfortunately the Drupal 6 version of the Date module is no longer supported. That said, we appreciate that you took time to work on this issue. Should this request still be relevant for Drupal 7 please feel free to reopen it. Thank you.