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's trivial and why shouldn't we do that?
I committed a change to feedapi_node already, so that module won't mess with the teaser: http://drupal.org/node/491594#comment-1852122
Comment | File | Size | Author |
---|---|---|---|
map_teaser.patch | 1.38 KB | Aron Novak |
Comments
Comment #1
Aron NovakShould be in FeedAPI mapper 2.0 beta 1
Comment #2
alex_b CreditAttribution: alex_b commentedNot critical for 2.0 beta 1.
How will this work when there are two different mappings to teaser and body? I'm not sure whether we can handle possible conflicts.
Comment #3
gordon CreditAttribution: gordon commentedI think this should actually be put across multiple lines
Also the problem that this patch doesn't allow for is that fact that you can't map the same field to multiple places. In the case of the body and teaser I would think that most of the time the same thing will get mapped to both since most feeds are only the teasers.
This review is powered by Dreditor.
Comment #4
Antinoo CreditAttribution: Antinoo commentedSubscribing.
I'm getting empty teasers when retrieving nodes using FeedAPI+FeedElementMapper. :(