It would be good if a same image could appear in multiple galleries (as an example: a photo of a cat playing with a dog could be listed under the "Cats" AND the "Dogs" galleries.
I have implemented this by modifying the "Node reference" field of the "Image" Content type into "Select list", with an unlimited number of values.
I wonder whether this could potentially create any problems?
Comments
Comment #1
Macronomicus commentedIf you used image_fupload (and use the one image per node setting) you can easily add taxonomy to each image. Then you can have more fine grained control over displaying images, by tagging them accordingly and calling them up in various galleries.
That is a cool idea about the reference with multiple values but it may become unmanageable once you have a multitude of galleries, that select list could get really huge.
Comment #2
karens commentedThe problem is that this module uses a lot of tricks to get the image into the right gallery using arguments and nodereference_url, tools that expect a single value. It might be doable, but would take some thinking to see if and how.
Comment #3
karens commentedNo one else has any ideas and I don't either.
Comment #4
karens commentedI'm going to leave this active so people can find it, since it's been requested several times. But no one has provided any easy solutions, not sure it will be done.
Comment #5
bewhy commentedAssuming that you have Image and Gallery content types . . .
You need the nodereference module.
In the Image content type, add a nodereference field called field_gallery. In the configuration of that field, in the global setting section you can alter the "number of values" option to more than one. I am testing both the nodereference url and the nodereference explorer modules.
That should work, at least some. Now, as to the next few steps, i.e. how to play around with views and whatnot, i'm not the guy to ask, I just figured this (above) out while looking for what you're looking for! I also know of a module called something like nodereference reverse lookup that allows for more views or something, but I haven't even explored that.
***be wary of***
http://drupal.org/node/876742
Modules suggested to play with:
http://drupal.org/project/nodereference_explorer
http://drupal.org/project/reverse_node_reference
http://drupal.org/project/nodereference_url
Video to watch:
http://www.lullabot.com/articles/photo-galleries-views-attach
Explanations to read and understand what's going on:
http://drupal.org/project/cck_gallery
http://drupal.org/project/node_gallery
Comment #6
karens commented@BeWhy, we are already using nodereference on an image content type and Views Gallery is an accumulation of all the techniques illustrated in the video you pointed to, so I suspect you haven't even used this module.
The current system is built on an assumption that images will only have one home (the nodereference value). Ordinarily you could make the nodereference field a multiple value field, but because of the system that uses Views Attach and Nodereference URL to get the images in the gallery, it has to be a single value field. So as I said above, it would take quite a bit of thought by someone who has actually used Views Gallery and who has a pretty good knowledge of Views to see if there is a way to make this system work with a multiple value field.
Comment #7
bewhy commentedOh, okay. Glad to try to help.
Comment #8
bdone commentedWithin an image content type, is editing the gallery field's widget type from 'Reference to url' (nodereference_url), to a 'Check boxes/Radio buttons' going to cause other problems?
This seems to only remove the "Add photo" link beneath a gallery from the 'gallery' view.
@KarenS can you please elaborate? Are there other concerns aside from that view's output?