Closed (fixed)
Project:
Feeds
Version:
6.x-1.0-beta9
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Sep 2010 at 21:24 UTC
Updated:
5 Mar 2014 at 18:01 UTC
Jump to comment: Most recent
The call to empty() in the data processor of feeds is overly strict, making zero values exit the function immediately. This patch replaces it with a call to === NULL.
| Comment | File | Size | Author |
|---|---|---|---|
| zero_null.patch | 749 bytes | tmcw |
Comments
Comment #1
alex_b commentedComment #2
imclean commentedWorks for me, thanks. Could probably also use is_null().
Comment #3
imclean commentedCome to think of it, does it need this check at all? Inserting an empty or null value could be handy, especially when updating an existing field.
Will do some testing with it removed.
Comment #4
twistor commentedI went ahead and committed the patch since the use case is valid.
@imclean, did you come up with anything regarding inserting NULL values?
http://drupalcode.org/project/feeds.git/commit/a07f987
Comment #5
imclean commented@twistor, thinking about it some more, it really is up to the db to set a null value. An empty value can still be inserted with the above patch so this pretty much takes care of my concerns.
Comment #7
p0832414 commentedAny solution for D7 ? I cannot find where to apply this patch. Any help would be appreciated...
Comment #8
jay-dee-ess commentedReopening. I ran into this issue in 7.x
Comment #9
jay-dee-ess commentedSorry. Reverting back. I now see this is being addressed here: https://drupal.org/node/1107522