I realize this is out of scope, but I didn't find any other active Flickr-handling modules
I'd like to use Flickr as my image-file management platform, but when displaying images on a given Drupal site, download the highest-resolution version, processing it according to a designated imagecache preset (e.g. "largest-allowed") - presumably also governed by filesize/resolution max limits set elsewhere as appropriate.
Of course the next question is where to put the image? A-in the filesystem B-what image-handling module, Image or Imagefield?
- A - ideally any folder under files/ - set a global default, and allow the user to designate/create a different one per photo-set
- B - ideally let the user choose between Image or Imagefield
- Realistic option: whatever method you like, as long as you support 1:1 image-as-node. Therefore if Imagefield, user must designate a content type in which the first (only?) imagefield is single-valued, and a separate node is created for each image.
- Back to the ideal scenario, have an option allowing a content type where a selected "primary" photo gets inserted into the first single field, and then the whole photoset (including another instance of the "primary") gets inserted into the second multi-value field.
This would allow a teaser display/View to show a single thumbnail of the primary, while the whole set gets shown in full node display. Basically supports custom Galleries from the get-go too.
And (back to the import config point) allow a taxonomy term to be applied to the generated node(s) as with Image Import.
Should be able to code it up over the weekend eh? :)
Comments
Comment #1
Anonymous (not verified) commentedPlease reopen if you still need assistance
Comment #2
Anonymous (not verified) commentedComment #3
HansBKK commentedIf anyone from the future happens to hear of an upcoming enhancement or other module that might help with this, please post back here.
Comment #4
Shai commentedhttp://drupal.org/project/emfield
I'm pretty sure the Embedded Media Field module either currently does it, its dev version does it, or it is soon being added. Just heard Aaron Winborn (project maintainor for that module) speak at DrupalCamp Philadelphia and he mentioned this was an often asked for feature and that he was responding to that desire.
Note that this kind of functionality might possibly break Flick's Terms of Use --- or at least get very close to the edge, depending upon how it used used.
Shai
Comment #5
HansBKK commentedOh! Hi Shai, nice to see you, didn't realize. . .
Actually, the project page doesn't make this clear but this issue does. Emfield just stores a URL referencing off-site locations, it doesn't pull down a local copy of the image, which is what I'm looking for.
So leaving the call to future people here for now, but I recognize it's likely to happen first in Emfield.
Actually, what I'd really like is creation of a set of standalone Image module nodes, all tagged with (via taxonomy term) the name of the photoset.
Thanks for your time
Comment #6
sreynen commentedThis wasn't actually fixed, was it?
Comment #7
lolandese commentedCleaning up the issue queue.
Marking as a dup of #871144: [snippet] using imagecache to resize photos. Even if this issue is older, the other one provides some code.
Feel free to reopen if there is a reason for it.
Thanks.