Closed (fixed)
Project:
Feed Element Mapper
Version:
6.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Jun 2009 at 09:15 UTC
Updated:
27 Jul 2009 at 20:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
alex_b commentedThe reason for keying the descriptions array by module and field name is that thus more than one module can offer mapping for a specific field name (e. g. an alternative taxonomy mapper).
Comment #2
aron novakBut it seems that $field_name is always empty.
(edit: it's about the description generating, not about the select form item's list)
Comment #3
neclimdulYeah, as Aron noted in the first post, $field_name is undefined in _feedapi_mapper_get_field_mappers_descriptions which is causes the weird line he pasted in #2 to be needed. We never actually take advantage of this field_name separation in our code at any point and the descriptions are so separate from the field names that its probably best to remove this.
Comment #4
neclimdulAlso, #397650: Improve and separate mapping UI makes the separation even more prevalent. Think we should go with this.
Comment #5
alex_b commentedOk. This is committed.
I had to clean up a small problem with determing available modules (iteration did not step into nested sub fields).
For the record, the patch that got committed.
I am not 100 % happy on how feedapi mapper filters out descriptions after querying them by a test against $field_map because this test is a bit messy. But this goes beyond the scope of this issue.
Thank you!