This is undoubtly the best gallery module available for DNN that I have found and I would really like to say Great job guys!

Right now though it is either public or private with no wiggle room in between. I would very definitely like to use this on as a private album on a private family site and I don't want end users editing/deleting other users albums. It's already very, very close to exactly what I need. In my world, I want any authenticated user to be able to add an album from the root folder. Only the owner of that album can add more albums to his/her existing album and access maintenance for his/her existing albums but anyone can add an image to any album while only the image owner or the ower of the album should be able to edit that particular image

A Private gallery does not work because it is limited to a specific user. So, I have toyed with the menus that get added using a method I added in Authorization as:

Public Function HasMaintenancePermission(ByVal DataItem As Object) As Boolean
  If HasAdminPermission() OrElse IsGalleryOwner() OrElse CType(DataItem, IGalleryObjectInfo).OwnerID = LoggedOnUserID Then
     Return True
  End If
  Return False
End Function

Public Function HasItemMaintenancePermission(ByVal DataItem As Object) As Boolean
  If HasAdminPermission() OrElse IsGalleryOwner() OrElse CType(DataItem, IGalleryObjectInfo).OwnerID = LoggedOnUserID Then
     Return True
  End If
  Return False
End Function

So these methods control what options get added perfectly when I am on the root project however when I get to a sub album I am not getting an edit on the image for the owner which I want. I have it in both menus but obviously I am not testing the image object correctly in the HasItemMaintenancePermissions? Any thoughts here?

But the killer for me to roll this out is, after an album is added, the maintenance screen is shown and the user has full permissions to delete or edit anything. I need to stop this but just can't find where or how it is called. Can anyone point me in the right direction on how to stop the maintenance listview after the add of an album? This would work just fine for me if I can control this.

It would work even better for me if this type of granularity could be rolled into the standard product so I would not have to modify the code everytime a new version is rolled out ..~grin~...

Thanks in advance for any help.