Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It seems odd to me to have the feed_nid property exposed as a mapping target, but I don't know enough about Feeds to be certain...
Comments
Comment #1
MegaChriz CreditAttribution: MegaChriz commentedI don't see this property as a mapping target (using the latest dev of Feeds). Can you provide the steps needed to have this property available as mapping target?
Comment #2
joachim CreditAttribution: joachim commentedI was using Feeds with Data module to import from a CSV file to a Data table entity type.
Comment #3
MegaChriz CreditAttribution: MegaChriz commentedAh, I see. This mapping target is only available when using the "Generic entity processor". And it is available due to the following code from plugins/FeedsEntityProcessor.inc, ± line 244:
"feed_nid" is defined as an entity property in
feeds_entity_property_info_alter()
and as a result it became available as a mapping target.It doesn't look intentional. There is also no information available about why this is a mapping target in #1033202: [Meta] Generic entity processor.
I think this property should be removed as a mapping target.
Comment #4
MegaChriz CreditAttribution: MegaChriz commentedMoving to the Feeds entity processor project, the new home for the generic entity processor.
Comment #5
MegaChriz CreditAttribution: MegaChriz commentedThe property "feed_nid" is no longer exposed as a mapping target. Mapping targets are created only for properties which have a setter callback now. This was changed in the following commit: http://drupalcode.org/project/feeds_entity_processor.git/commit/f7e70db
So this is no longer an issue.