Closed (fixed)
Project:
Default Node Gallery
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Jun 2011 at 13:47 UTC
Updated:
16 Aug 2011 at 08:44 UTC
We want to have default gallery for every user to make image sorting easy and to streamline the uploading process.
Comments
Comment #1
fastforward commentedOk. We can remove it by
So. It's complete solution. Unless there no pitfalls.
Comment #2
scroogie commentedThanks for the writeup.
It should be documented somewhere official imho.
Comment #3
fastforward commentedSince I am not a programmer - it's probably the best solution that I can use on my site. But at the same time, I believe that really good gallery software should practice two basic principles:
1. Users should be able to add a picture as quickly as possible. People come to website not to assess its powerful functionality. They simply want to "Submit Image". Therefore, the "right" gallery-site should provide the ability to add images any time, and from any page.
2. If there is additional formalities that delay time of uploading images, we must remove them, or make optional.
If you force users at each upload, again and again choose a gallery, they get tired of it very quickly. They say $@%&!!!
People tend to be inattentive. When they second time forgets to select option in "Assign to Gallery" list and quite unexpectedly see the "Unnamed Gallery" form, they shout $@%&!!! and go forever. There is no doubt that really good gallery software can't to impose a default need to create (or select) a gallery. There is following solution.
Node Gallery must create basic (default) gallery for each new user (call it Photostream) and provide an opportunity to quickly add images, without being distracted by side issues and functions. One, two, and ready! The drop-down list on the node/add/node-gallery-image should contain "Your Photostream" as First (default) its option. The user can constantly create new galleries, or may not even bother about it. In any case, it will get the image to the right place and would not swear once again seeing the "Nameless gallery". So, I think it is only two points: 1) Create default gallery (Photostream) and 2) Make it (Photostream) default option in list. Voila!
I would hope you will reconsider the default behavior of NG and this module (the best gallery module for Drupal, imho) will be truly cool... Thank you
Comment #4
scroogie commentedWell, I'd say lets do this. Justin, what do you think?
Comment #5
dddave commentedThis sounds like a very reasonable feature request. Would it be much work (ie postpone to NG3.1) to code this?
Do we want to call it "photostream"? Or can we think of a more unique name?
Comment #6
dddave commentedComment #7
fastforward commentedYou're right, dddave. The issue of internal names ("Gallery", "Photostream") - it is a very important question. For each particular site it is a matter of branding and specific topics. For example, in my case words "Set" or "Collection" would fit much more than "Gallery". I looked at the code and realized that I have to change so many files in core for one or two words in each. I had to abandon the idea. Similarly, with the name of default_gallery - the user should be able to change the default name (e.g. Photostream) for some unique, in its sole discretion.
It would be great if two new options appeared in administrative panel for Node Gallery:
1) "Alter the common name of the gallery: ..." (i.e., word "Gallery")
2) "Alter the name of default gallery: ..." (e.g., word "Photostream").
Comment #8
justintime commentedI'm good with it, but here's some thoughts:
- We need to be able to only have one active relationship that will create a default user gallery upon user login. IE, if I have 3 relationships, and create 3 default galleries, which one should be first? With this in mind, I think a checkbox to enable this on the global settings with a dropdown of available relationships would be the way to do the admin UI.
- While it sounds like a good idea to do this at user creation, I think it's better to look for the existence of a gallery at user login. That way, if you enable the feature after you already have 2,000 active users, they will get the gallery created for them as they login.
- What happens when a user is deleted? Do we delete their gallery? I'm thinking no.
- How do you link the default gallery to the user? IMO, we'd need a new table to link UID to GID.
- While photostream may be more appropriate, the module is named Node Gallery, and we have the string Gallery all over the place. Could we just use "My Gallery"?
re: 3.0 or 3.1, I don't think it should block 3.0. We're just too close, and we're already in beta.
Comment #9
fastforward commentedDreams come true! Thank you, Justin! Creation of gallery at user login - is exactly what needed! Just in case - small, but significant remark on the subject. Navigation at default gallery, of course, must be organized in the same way as in conventional galleries, ie with the carousel and anchors. The more images in gallery - the more sense to use the carousel. Therefore for default gallery carousel is simply irreplaceable. I guess I said something self-evident, but it's just in case))
Moreover, if there was a choice: one carousel in default gallery or a lot of carousels in conventional galleries, I would certainly chose the former, because it's much more easier and more enjoyable to leaf through one long gallery, than constantly jump from one short gallery to another.
Comment #10
fastforward commented.. And, of course, the default gallery, in any case, should contain ALL images of particular user, to be able to look through all the user's images with a single carousel, to be able to see them together, in one stream. The user can create a hundreds galleries for his images, but in any case, all this images should be available from his default gallery.
- "My Gallery" - will be fine!
- "What happens when a user is deleted?.." Logically, all user information must be destroyed. But when it comes to galleries, the images (especially if this is a high-quality images) - is a content that, in terms of community and the owner of the website may represent a great value. So, I think it would be wise if the site administrator can choose between removal and preservation using a checkbox in the admin UI.
Comment #11
justintime commentedMarking as postponed until at least 3.1.
Comment #12
scroogie commentedSo post #10 contains a different description. In that case it wouldn't be a "real" gallery, it would just be a view of all images of that user. We will have to discuss which way to take. I agree on postponing this, we should keep this on our list, though.
Comment #13
crea commentedSubscribing
Comment #14
crea commentedIs it good idea to implement this in a separate module ? This feature is very important for my site and I can work on it.
Btw, great job on the module. I was planning to implement something like this, and then found it. Excellent candidate to migrate to from the acidfree module.
IMO, it only makes sense to have "unsorted" images in the default gallery. It's sort of junk box, for the user to work with and to sort images. After image is put in a separate, non-default gallery, there's no reason to show it inside the default one.
If you show all images in the default gallery, you are making image sorting very difficult task without any real advantage.
I see in some cases showing all user images could be useful, but it's different from the "default gallery" feature because it solves completely different problem - to give user overview of his images.
Comment #15
justintime commentedI think it would be a better fit in it's own module. Perhaps it could be married into the node_gallery_user_profile module? It could eventually get collapsed back into NG, but timing is the issue now.
I wouldn't want to commit a large new feature into what I hope is the last beta before final 3.0 release.
Comment #15.0
crea commentedCreated summary of module requirements in the issue summary
Comment #15.1
crea commentedmoved my comment about multiple relationships
Comment #16
crea commentedI've moved the summary to the project page
Comment #17
crea commentedComment #18
dddave commentedAwesome man. Go for it. I'll happily test anything that you provide.
Comment #19
crea commentedI've committed first code. Please open separate issues for additional questions.
Comment #20
dddave commentedI am going to play around with this module over the weekend. Looking forward to it.
Comment #22
fastforward commentedWow. I can't believe. This happened. When NG-guys said that this issue postponed, I decided that all would happen no earlier than a one hundred years (or two). Impossible is nothing, really. God bless Drupal and its courageous developers (and its brave community, sure)).
Thank you, crea! This module, no doubt - exactly what NG need. Pity, that I have already started doing things the way I described in first revision of this issue. Yesterday I had two tries to install Default Node Gallery, but both had no succeed. Perhaps this module needs clean install to work properly. But I've set up about 90 mods at the moment and it's not the end. Any way, I'm going to try again from fresh D6 as soon as I would have enough time!
Comment #22.0
fastforward commentedMoved module description to comments