Lack of documentation

Yeah, user documentation will be done by the 1.0 release.

The module is really simple though so here is a quick rough draft of usage steps:

1. Install simplepie.inc into the Feeds module by following the instructions in their README.txt file. If you have done this correctly you will see a "SimplePie Parser" as a parser option.
2. Enable the feeds_flickr module.
3. In the Feeds configuration under Parsers you will find a new parser called Flickr Parser. Choose the Flickr Parser.
4. You will now see new elements to map in the Mapping section.

Of course these steps are a quick dry run it will need to cleaned up and things like admin paths inserted, etc. But that will get you going. This of course assumes you know how to use the Feeds module that this module is dependent on.

I've put simplepie.inc in /sites/all/modules/feeds/libraries and I've activated Feeds_Flickr module.
But no Flickr Parser available.
What could I've missed ?

@srobert72: You should remember to clear your cache after you have place the simplepie.inc file in the correct folder so that the libraries are re-read.

@rbl: That is the correct functionality. You can simple use the URL for src attribute of a img tag or use it in any other fashion you would like. ex: provide links to all the thumbnails and original as text links, link icons representing the sizes, etc. The URL is the most flexible method. If you are using Views to output your data you can simple use the "Rewrite..." option to place put the URL in the correct tag or other function. Otherwise you can affect the output through either the theme layer or possibly CCK formatters if you are importing into nodes.

@dragonwize
Thank you, you're right, that was my problem.
I've launched /admin/build/theme, I supposed it would reload simplepie.inc.
But empty cache had better effect.

Going to /admin/build/theme only rebuilds the theme registry, it doesn't touch any of the other caches.

Documentation would be really useful. The whole integration with SimplePie for instance (which is itself a module which isn't well document or possibly even supported).

Documentation is in comment #1 above.

This module does not integrate with the simplepie drupal module. It just uses the simplepie library. All the documentation needed to use it is in the Feeds module documentation. There really is no setup for this module at all, it just works. But you do have to setup the Feeds module correctly, so if you are having trouble there please help the maintainers out over there.

I just set up the Feeds module for the first time yesterday. But I do have it working.

Many need a Flickr API key, but your app seems to just pull down the large thumbnails, right?

The feeds module came with two content types, but I need to create two new content types in order for this to work along side the other one (which is working fine).

Simplepie's README.txt I believe is in their lib directory not in core. I did bring in simplepie.inc into the library directory in the Feeds library and it seemed to work to show up on the Feeds admin screen.

However, I couldn't get it to import the images as nodes. Any more direction would be good.

Only the Flickr API requires an API key. This module as the is said on the project page and the name suggests, works with Flickr RSS feeds.

If you want to pull in via nodes you have to select the correct options in the feeds importer you created. That is also where you will set your mappings, which is what this module does, by allowing you to select more options from a Flickr feed than the normal mapping options.

I have installed simplepie and have flickr as the parser but I'm still not sure how to map the "media" sources from the flickr feeds module. How do I make targets for media link, media link, etc. I'm guessing I do something with content types? any help on how to set targets would be much appreciated. thanks

@apes132
You manage the targets in the "mapping" section of the feeds module settings.

hi dragonwize

I'm sorry I wasn't more clear, I understand where to find the mappings but I don't understand how to add targets that apply to the all the "media:". Such as why do I use media link compared to item url? or the media credit field, how to I make a target that applies to media credit

I am sorry, I completely do not understand what it is you are asking.

ok i will try again. there are targets
Title The title of the node.
Body The body of the node. The teaser will be the same as the entire body.
User ID The Drupal user ID of the node author.
Published status Whether a node is published or not. 1 stands for published, 0 for not published.
Published date The UNIX time when a node has been published.
URL The external URL of the node. E. g. the feed item URL in the case of a syndication feed. May be unique.
GUID The external GUID of the node. E. g. the feed item GUID in the case of a syndication feed. May be unique.

but with the feeds flickr module new fields from sources how up:
Media: Title Media:title field.
Media: Description Media:description field.
Media: Credit Media:credit field.
Media: Category Media:category field.
Media: Link Media:content url field.
Media: Width Media:content width field.
Media: Height Media:content height field.
Media: Thumbnail 75x75 Media:thumbnail field sized at 75x75 pixels.
Media: Thumbnail 100 Media:thumbnail field sized at 100 pixels on the longest side.
Media: Thumbnail 240 Media:thumbnail field sized at 240 pixels on the longest side.
Media: Thumbnail 500 Media:thumbnail field sized at 500 pixels on the longest side.
Media: Thumbnail 1024 Media:thumbnail field sized at 1024 pixels on the longest side.

so for instance how do i set a target that means "Media:credit", there is not a target field that corresponds to this.

hope that makes more sense. sorry for all the confusion

Still not entirely clear on your question but it sounds like you are asking what fields to map those to. You can map those entries to any fields you want or none at all. They are there for you to use however you wish. If you are asking how to create the fields, you can do it with CCK, a custom module, a contrib module, or even just stick it straight into another data store like a table or flat file, the same way you create a store for any other kind of data in Drupal.

I created a cck text field for Media:credit, I figured the media credit would be the person's flickr account name, but I'm getting a long string of for example: bed14d7872c68d772ed041a408f2fed2.

can someone please explain to me what Media:credit is extracting from the flickr rss feed?

thanks

The field is whatever Flickr provides. Look at the RSS feed to see the elements being pulled.

I'm getting the same issue with Media:category. I have a single tag in the RSS feed for a particular image:

<media:category scheme="urn:flickr:tags">blue</media:category>

However, drupal is storing 2dcfd53f2ef2d088602d2381a5adb410 in the tag field.

The source Media: Category is being mapped to a textfield name "tag".

If you are having issues please fill out a separate ticket instead of continuing this thread which is about documentation. And please remember to include a link to the RSS feed you are attempting to parse.

I've created a new issue. Thanks kindly

A fix for the media:credit and media:category fields has been committed. Please file any problems not directly related to documentation in another issue.

Hi all, in the module page there is the following description:

Additional fields available to map:

* media_width = Original photo width
* media_height = Original photo height
* media_title = Photo title
* media_desc = Photo description
* media_credit = Photo credit
* media_category = Photo category
* media_thumbnail_75x75 = Thumbnail URL, 75x75px
* media_thumbnail_100 = Thumbnail URL, 100px on longest side
* media_thumbnail_240 = Thumbnail URL, 240px on longest side
* media_thumbnail_500 = Thumbnail URL, 500px on longest side
* media_thumbnail_1024 = Thumbnail URL, 1024px on longest side

But I can't find theese items in the sources options (see the image in attachment): why ?

Thank you very much

@MXT: You have the simplepie parser selected. You need to have the feeds flickr parser selected.

You are absolutely right: thank you very much!

i got it work.. but there is no README file.

* the easy way is to put simplepie.inc into libraries folder of feeds module.
* now clean your cache
* the simplepie parser should now be avaiable with the specified fields

what i'm missing is not only the missing doc's, but a caching method of the images like flickrrippr module.
so we can use it in combination with imageapi/cache for manupulations. i'm using code from
flickrrippr jpeg cache in a computed field... proof works nicely.

So, could someone confirm that:

Media: Category

... is the tags?

Just wanted to add that the feeds documentation says to install simplepie that you need to name the file simplepie.compiled.php which did not work for me until I named it simplepie.compiled.inc which allowed me to see the simplepie parser option but not the flickr parser option. It wasn't until I renamed the file to just simplepie.inc that I was able to see the flickr parser option. Just putting that out there in case it helps anyone else.

@hollybeary, see #2063189: Compatibility with Simplepie 1.3 for the issue mentioned in #28.

I am really confused....
Where can I find the simplepie.inc and where should I put this?
I can only find simplepie.php , I have uploaded that on fees/libraries folder but nothing.
I have also applied the patch from here https://drupal.org/node/2063189#comment-7745087
but still I cannot see the Simplepie parser..
Anyone help please?

@hollybeary: I renamed simplepie.php to simplepie.inc and put it inside feeds/libraries folder and also inside inside libraries/simplepie folder ,but no parser appeared neither simplepie nor flickr parser.
What should I do?
thanks

This module was built for an older version of feeds and has yet to be updated, takers anyone?, so your mileage in getting it to work with newer feeds module is unknown.