Mapping media enclosures [#363725]

I have a feed (parsed via the simpliepie parser) which provides the the feed information as below.

I would like to be able to map the options->enclosures->video->x-m4v->link to a custom cck field, but the mapping through the feed element mapper is only giving me options->enclosures->video->x-m4v.

Is there a way to get the mapping to drill down further into the array?

I'd really appreciate any help available.

Comment	File	Size	Author
#16	feedapi_enc_link.patch	625 bytes	kswan

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

benced CreditAttribution: benced commented 30 January 2009 at 11:32

I'd like this too am going to look into the code to see why it is restricted to three steps down the heirarchy of the array

Comment #2

benced CreditAttribution: benced commented 30 January 2009 at 10:17

Found what's blocking it

These lines here

      // Arrays with keys of 0 are not considered collections of same items - reached a leaf.
      if (isset($items[$key][0])) {
        unset($items[$key]);
        return $path;
      }

i.e. anything stuck under an array beginning with

[0] => Array

will not come up as an option

Will try deleting these lines of code and see what happens, I'm sure there is probably a reason why this is there though :S

Comment #3

benced CreditAttribution: benced commented 30 January 2009 at 11:34

I'm guessing this was done to save on memory as the element mapper seems to use a lot of memory (esp after selecting the Simplepie Parser)

I've tried removing these lines of code and eventually had to extend my php memory limit to 1024M and there still was not enough memory to run the script, I'm hesitant to try extending it further

I've tried adding the selection using PhpMyAdmin with no luck yet
I've tried a few things including adding a custom default option, which didn't work

I think this may be because it merges all the feed items into one item and if I could find a way to switch that off and for the map to map just one feed item, which breifly looking at the code I can't find a way of doing this despite there being some suggestions that you can, then removing the lines of code might be able to work without taking too long or using too much memory

Anyone else know how to do this?

Comment #4

benced CreditAttribution: benced commented 30 January 2009 at 12:50

Going to try using this method instead -> http://drupal.org/node/170338

Comment #5

benced CreditAttribution: benced commented 7 February 2009 at 03:23

Problem solved

In between line 188 and 189 in the simple parser module I added this

$curr_item->enclosure_link = $simplepie_item->get_enclosure()->get_link();

Now I can map this using the mapping interface to map the link to the enclosure item wherever I want to embed in a player, to display, whatever...

Comment #6

benced CreditAttribution: benced commented 7 February 2009 at 03:26

Version:	6.x-1.x-dev	» 5.x-1.0-beta7
Category:	support	» feature
Status:	Active	» Needs review

Changing to what my settings are,

Perhaps someone can make a version up for Drupal 6

Comment #7

benced CreditAttribution: benced commented 7 February 2009 at 10:20

Code now wrapped in an if statement so that the link isn't searched for when it don't exist

if (is_array($enclosures)) {
    $curr_item->enclosure_link = $simplepie_item->get_enclosure()->get_link();
    }

Comment #8

bigjim CreditAttribution: bigjim commented 19 February 2009 at 22:12

Using feedapi 6.x.1.6 #7 works except insert it at line 155 in lieu of 188

Comment #9

ball.in.th CreditAttribution: ball.in.th commented 18 March 2009 at 17:08

Hi,

I think the proper way to do this is for the mapper to handle an array of elements. You can just pick "options->enclosures->video->x-m4v", and the mapper should see that it's an array and maps properly. If it doesn't, perhaps its a bug in the mapper. For example, see the feedapi_mapper_emimage.inc:

      elseif (is_array($feed_element)) {
        foreach ($feed_element as $element) {
          if (is_array($element)) {
            // is this an options->enclosure-media->type array
            if (valid_url($element['link'])) {
              $items[]['embed'] = $element['link'];
            }
            elseif (valid_url($element['player'])) {
              $items[]['embed'] = $element['player'];
            }
          }
          elseif (is_string($element) && valid_url($element)) {
            // not sure when this would be called but for completeness
            $items[]['embed'] = $element;
          }
        }
      }

Comment #10

alienresident CreditAttribution: alienresident commented 15 April 2009 at 21:56

I also had to make this change to map .mp3 enclosure for a feed directly from iTunes itself.

Thanks for the code it worked like a charm.

Comment #11

Anonymous (not verified) CreditAttribution: Anonymous commented 11 November 2009 at 18:02

Version:

5.x-1.0-beta7

» 6.x-1.x-dev

An even better way would be to allow a custom mapping, instead of the fixed dropdown. For example, a textfield to enter: options->enclosures->image->jpeg->0->link which can be mapped to a custom cck field.

That would accomodate for every possibility...

Comment #12

mickfuzz CreditAttribution: mickfuzz commented 11 November 2009 at 19:38

I've got a situation pretty much exactly the same but with an Audio file.

What is the code in #7 that you added supposed to do benced?
I've added it but can't see any extra elements in the mapper. Only as you point out upto the
[0] => Array - point

It would be good to find out what the deal is.

Comment #13

dman CreditAttribution: dman commented 19 November 2009 at 09:54

RE #11

FYI, I just found feedapi_parser_exhaustive which exposes every bit of data in the feed in a structured way for you to choose from.
It's not as 'clever' as the other ones like simplepie or FeedAPI Extensible Parser that strictly offer an interpreted subset of the half-dozen feed formats out there. This one just throws all the data back at you. Cherry-pick the field from an exposed array. No code.
Also handy for non-standard 'extensions' to RSS!

Comment #14

whatdoesitwant CreditAttribution: whatdoesitwant commented 19 November 2009 at 22:55

Thanks dman. I was wondering what was causing all my errors. I did not understand from the documentation that feedapi_parser_exhaustive and simplepie parser are interchangable and not supposed to be used additionally like feedapi_scraper. The activation of feedapi_node results in the suggestion to install parser simplepie. I therefore assumed feedapi_node and parser simplepie to be joined at the hip. I then assumed that feedapi_parser_exhaustive was an add on to parser simplepie. This is a misconception.

Am I correct in stating the following?
Within the feedapi package, in a nutshell you can install:

feedapi to mark a content type as a feed.

feedapi filters to filter feed items: feedapi_dedupe, feedapi_tagger.

"primary" (stand alone) feedapi parsers to make feed item data readable to drupal: feedapi_parser_exhaustive, or parser simplepie.

"secondary" (add-on) parsers to help primary parsers: feedapi_scraper for parser simplepie.

feedapi processors to convert feed items to nodes (feedapi_node) or to pass on feed settings to feed items (feedapi_inherit).

feedapi add ons to do cool stuff: to map parts of feed items to fields (feedapi_mapper) or to get pretty images (feedapi_imagegrabber).

Comment #15

dman CreditAttribution: dman commented 20 November 2009 at 06:57

That's a pretty good explanation of my understanding ... although the first time I saw the suite at all was yesterday :-)

We need a nice big picture of the jigsaw.

Slightly disconcerting is how feed parsers may not have settings that show up (not all need them) on the feed-nod form so it's tricky to tell when they are enabled and working.
I'm still unsure on the exclusiveness of the base+add-on parsers ... and what effect the weight has when they don't over-write each other anyway, but I've created a recipe that fits for me... for now.

Comment #16

kswan CreditAttribution: kswan commented 10 December 2009 at 04:41

File	Size
feedapi_enc_link.patch	625 bytes

I think that the normal use for the "enclosure" tag is to get the file url. The attached patch adds an "enclosure_link" item to the "Feed items" so that you can easily map the enclosure url to a text or link field.