Posted By wwatson23805 on 8/3/2005 9:07:18 PM

Thanks. I too would love to see this implimented. But there is another level of complexity here that you may also want to consider.

People form their own little groups--and you want to be able to accommodate group sharing. I would like to see it where if a user creates a gallery, they can specify by user name, who else may post or delete their own photos from the gallery.

Case in point: Say you put up a Page for a meeting group in, lets' say Richmond, VA. On that page you add a mini forum, and a news article section. You put an image gallery there. The Richmond group has 10 members. There's no sense in having 10 separate galleries for 10 separate users--so they create one gallery, and give all 10 users the rights to add and remove their own photos from it

Posted By bmolzen on 8/4/2005 6:44:38 AM
*drool*

Posted By Zivan Van Zyl on 7/11/2005 11:47 PM
For me, it would be marvelous if :

1) The user can subscribe to a certain role that (once payment has been received) allows them to create one album. I think (and I may be wrong here) that this is already possible via DNN (setup a role for subscription and give that role edit permissions on the module instance?).

2) From there on out, adding and editing images is simply restricted to whoever created the album, and administrators of course. That way, you may not have to keep any security settings on the album level - other than storing the user who created the album - since whoever creates the album is always assumed to be the editor of the album. Later on, you could add functionality to allow the admin (or maybe even the creator of the album) to arbitrarily add users to the list of users allowed to edit the album. It may be prudent to allow administrators to at least change the "owner" of the album just in case the admin has to create the album for the user, and then let him edit it from that point on.

3) Finally, I would like the user to have the ability to set a "view" password for the album so they can restrict viewing of the album to friends and family they give the password to.

So basically, album creation at the module level via security roles, and album editing at the album level (by checking the creator). The "view" password thingy will have to be stored at the album level as well. That would do it for me :-)