I posted this in the Image group but haven't got any response yet. May be because the title is about user-managed galleries but in fact it is about user managed node hierarchies ;-)
One of the most frequently asked questions in Drupal's forums is how to create image galleries. Quite often the questions are about user-managed galleries but because they are not asked in a clear way, they usually get answers that are not useful. A number of solutions exist that can help the site administrator or editor set up a gallery but so far I haven't seen one complete native Drupal 6 solution that can handle user-managed galleries. Acidfree is probably the only one but it is far from ready for D6. So here is simplistic description of a typical user-managed gallery that I want to build on D6. Similar functionality can be found in Gallery2, Picasa, PhotoBucket, etc. I will appreciate if those of you who have build such things provide any tips or how-to materials ;-)
Requirements:
- Every authorized user should be able to create multiple galleries/albums
- A user should be able to add and remove pictures to/from any gallery owned by him/her and also change the parent gallery of an image
- A user should be presented with an efficient interface for managing the galleries and pictures within them.
- Images must be presented as paged thumbnailed lists with options (icon links) for deleting and editing (and possibly reordering) adjacent to each picture
- Galleries must be presented as paged thumbnailed lists with options for deleting and editing adjacent to each picture.
- When galleries are displayed to other users those editing/deleting options should not be available
- An image should only exists in the context of a gallery. Thus:
- It should not be possible to create an image without specifying a parent gallery
- When a gallery is deleted, all images in it must be deleted as well (automatically). No orphaned images are allowed.
More can be added to the requirements but let's stick to the basic structure for now.
Constraints:
- To allow seamless integration with Views, Panels, etc. the galleries must me Drupal nodes.
- For the same reason images should also be nodes although this is not that important as long as the requirements can be met.
- I would also exclude Gallery2 and any other non-Drupal package. Bridges always cause problems in the long run and using views/panels will be a challenge as well.
- No custom coding! ;-))) Configuration, setting up views, CCK types, blocks, basic theming - yes. Custom coding - no. The reason is that the functionality I am asking for is really basic and available on almost every photo site where users log in and submit pictures in their own galleries. It makes no sense to me to build that from scratch in PHP.
I have tried different solutions and the closest I got was to use Node Hierarchy + CCK and Views. The nature of this type of galleries is hierarchical. A very simple hierarchy though - just two levels. Node Hierarchy gives you the ability to create a parent-child relationship between custom node types (e.g. Gallery and Image). Using views one can create thumbnailed pages to show all the pictures within a gallery. You can also have a child order (custom order of the pictures in a gallery). The problem I found with node hierarchy was that it still cannot enforce the relationships. I.e. one can easily end up with images without a parent gallery.
I have also thought about using nodereference to establish the Gallery-Image hierarchy, but one can easily delete a parent without deleting the referencing children thus leaving the site in an inconsistent state.
I also tried a solution using imagefield and some custom theming but it does not work well for too many images. Imagefield's interface is not so good if you have 100 images in a gallery for example.
So my questions are: Why is it so hard to create a user-managed gallery in Drupal. How can one create Picasa-type of gallery in D6?
Thanks for the suggestions!
Comments
What properties for galleries?
What properties do you need for your galleries? Are they merely a container for the images, or do they also have descriptions, can be commented, et cetera?
My first thought was that images should be nodes, and galleries should be taxonomy (but could probably be nodes).
(I think you can manage deleting orphaned images with some actions stuff, but I'm not very good at handling actions so I'd better not say anything.)
//Johan Falk, Sweden
It is good if the galleries
It is good if the galleries are nodes because then it will be easy to add CCK fields (like descriptions) and use views to display lists of galleries. A gallery would have a title thumbnail image at the minimum.
I have thought about taxonomy but then what user interface is available to manage taxonomy terms (galleries)?
In Drupal a lot has been done to create user interfaces to present and manage nodes so that's why I want to leverage on that.
Same doubts
Hi I just started with D6 and expected Image Gallery to be fully developed and newbee/idiot proof. I still feel I belong to this group even if I have been struggling with Drupal for almost two years now, in spare hours.
While looking for info on how to custom-order/edit large sets of images I found a lot of stuff that only increased my doubts, not on only on HOW to manage things in Image Gallery but also on IF using IG really is the option, because it turns out there are many ways to manage Fotos and Galleries, but none seems to be fully satisfying:
Roundup of image modules for Drupal - http://www.davidnewkerk.com/book/35
Creating image galleries - http://drupal.org/node/207216
Drupal Imagefield Module Multiple Vulnerabilities - http://justin.madirish.net/node/338
I hope these articles can help you Kirilius, because to me it only got more confusing: more stuff to read, more alternatives to think about, more new options to learn...
Unfortunately I actually have no spare time to spend on learning Drupal, each minute on Drupal is one less for sleep or work (I have my own business) so I decided to stick to the "good" old Image Gallery, although I am worried about the large number of nodes that are created as indicated in one of the articles.
Also, the Image Import generates a boring and unending list on the frontpage of new posts (for each image...). This forced me too decide to use a non-dynamic frontpage.
And finally the image import interface is very limited. There are no thumbnails for the images, so if you need to give titles and descriptions on a large list of images only based on the img_0667.jpg filenames, you go absolutely crazy.
I'll continue trying anyway, let's keep each other posted on new findings.
Stopping New Images from showing on Front Page
Hi Riccardo
A tip to stop new images from being posted on the front page. You can set this default behaviour in admin/content/content types.
For the image content type, under the workflow tab, you get to set some options including whether the item should be posted to the front page by default.
HTH
regards
Charles
Interested too
Good topic this one...
I'm interested too in the solution of this and so... are there anything new for doing so ind DP7?
Thank you so much!!