Closed (fixed)
Project:
Flickr
Version:
7.x-1.x-dev
Component:
flickr (main module)
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
22 Jul 2010 at 06:19 UTC
Updated:
18 Jan 2015 at 14:03 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Marko B commentedwondering the same, is it possible and how?
Comment #2
Taxoman commentedRetrieving favorites would be equally useful as just getting ones own photos, and could trigger even more traffic, benefiting both the local site and Flickr, I would think.
FYI - Same feature request for other Flickr modules:
#994572: Retrieve images from Flickr favorites
Comment #3
Taxoman commentedComment #4
Taxoman commentedMarked #197141: Possible to fetch "favorites" and not only own photos? as a duplicate of this one.
Retrieving and "promoting" ones favorite photos from other people's photo streams seems like a very nice and powerful way of trigging even more interest.
I am frankly quite puzzled about the lack of interest for this particular feature (not just in this issue, but for several years in several issue queues: close to zero interest and certainly no progress anywhere as far as I can tell), which to me seems like an obviously useful feature, bordering on "important". Great for increasing traffic to own web sites by promoting other/best photos, etc., not just "own photos".
Comment #5
Taxoman commentedRef. my comment over at #994572: Retrieve images from Flickr favorites
"Maybe this module should be merged with the Flickr module to speed up developments?"
Comment #6
Taxoman commentedRelated-1:
In the Flickr API issue queue, #994568: Retrieve images from a users Flickr favorites confirms that the API already supports favorites, so it is up to contrib. modules such as *this* one to offer the feature.
Related-2:
#907164: Integrate with Flickr API
Comment #7
dakku commentedsee patch https://drupal.org/node/2023579
Comment #8
lolandese commentedDespite this thread being older, I'm marking it a duplicate of #2023579: Retrieve images from favorites - Block and API because that one contains a patch.
Thanks.
Comment #9
lolandese commentedFYI: this has been fixed in the duplicate issue.
Comment #10
lolandese commentedWhile 'favorites' was taken care of, 'gallery' would be still open as a feature request.
What a photoset is for a Flickr user's own photos, is a gallery for the photos of others they find interesting to put together in an album. This is more powerful than 'favorites' as it permits choosing photos of others and group them in an arbitrary way to embed an album the site.
Unfortunately we can't have the Flickr slideshow embed, but that doesn't work for 'favorites' either.
Comment #11
lolandese commentedImplementation for Flickr Filter. It allows for:
[flickr-gallery:id=72157645025390895, size=q, num=4, sort=views]As a side note:
Flickr galleries are intended for photos of others. It seems that mixing your own photos with others in a gallery leads to errors.
Thus:
Comment #12
lolandese commentedhttp://drupalcode.org/project/flickr.git/commit/5ed3c4d
Leaving active to extend to Flickr Block.
Comment #13
lolandese commentedExtended with two identical blocks that can be configured separately.
It matches the first found gallery from the node author's Flickr account that has a gallery title that matches a node's taxonomy term from the dedicated vocabulary, even partially and case-insensitive. E.g. it grabs a gallery titled 'All nice photos of Arabian horses I found of others on Flickr' on a node with the taxonomy term 'Horse'. Of course it does not filter on taxonomy terms within the gallery, something the text filter (Flickr Filter) does as we specify the gallery there and still have the tags available to filter on.
If there is no vocabulary selected in the block configuration it takes the newest gallery.
Comment #14
lolandese commentedhttp://cgit.drupalcode.org/flickr/commit/?id=266b571
Comment #18
lolandese commentedComment #19
lolandese commentedSee #2367755: D6 maintenance.
Comment #20
lolandese commentedSetting this back to D7 and being 'fixed (closed)'.
Main reason is the fact that links to this issue show the status on hover without revealing the version (6 or 7). This might give the impression that the mentioned issue will not be solved, while in fact it is already fixed for the D7 version. 'Fixed (closed)' reflects the current status correctly for D7. 'Closed (won't fix)' is only valid for the minimally maintained D6 version of the module.