Closed (fixed)
Project:
Feeds
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Oct 2015 at 13:36 UTC
Updated:
6 Jan 2016 at 13:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
megachrizAh, apparently in #1107522: Framework for expected behavior when importing empty/blank values + text field fix I forgot to include tests for all the "list" targets. I'm currently busy with other Feeds issues. Could you write a test for clearing out values for all the list targets and that confirms this bug? You could use
FeedsMapperFieldTestCase::testClearOutValues()from tests/feeds_mapper_field.test as an example. Put the test in a new file called "feeds_mapper_list.test". Else it could take a while before I have time to address this issue.By the way, great that you are trying out the Feeds import preview module! :)
Comment #3
troybthompson commentedUnfortunately, I'm not a programmer, and looking at the other test files in there, I don't think I have the skills to even hack something together. Sorry. Basically on my website, I mapped it to a boolean, integer, list integer, and text, and all but the boolean worked correctly when actually imported.
Yes, the preview has been very helpful to me to see what's going on while doing some crazy imports and conversions. Thanks!
Comment #4
megachrizNo problem, trobythompson.
Attached is a patch with an automated test only to demonstrate the problem. So the patch should fail tests. Writing this test was a bit harder than I had thought at first. For lists fields I needed to use
assertOptionSelected()instead ofassertNodeFieldValue(). For the boolean field this wasassertFieldChecked(). Took me some time to notice.A fix is not yet included.
Comment #6
megachrizIt think that this patch fixes the issue.
Comment #7
megachrizCommitted #6.