Make possible to map to the teaser [#552164]

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

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Aron Novak

Hungarian

Hungary, Budapest

CreditAttribution: Aron Novak commented 18 August 2009 at 10:35

Priority:

Normal

» Critical

Should be in FeedAPI mapper 2.0 beta 1

Comment #2

alex_b CreditAttribution: alex_b commented 23 August 2009 at 00:06

Priority:

Critical

» Normal

Not 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 commented 23 August 2009 at 23:56

Status:

Needs review

» Needs work

+++ mappers/feedapi_mapper_node.inc	18 Aug 2009 08:46:15 -0000
@@ -23,10 +23,10 @@ function node_feedapi_mapper($op, $feed_
-    return array('title' => t('Title'), 'created' => t('Published date'), 'body' => t('Body'), 'status' => t('Published state'));
+    return array('title' => t('Title'), 'created' => t('Published date'), 'body' => t('Body'), 'teaser' => t('Teaser'), 'status' => t('Published state'));

I 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.