I would like to make a usability suggestion. The menu that comes up when browsing albums as the root user. (Add a album,Add a photo,Add a video,Mass import) should be made available to all users that have permissions to add acidfree content. The reason I say this is some of my users are finding it difficult to add photos using the dropdown when their are a lot of albums.
I generally don't add content using the [create content >> acidfree media >> Acidfree photo] method. I browse to the album I want to upload to click Add a album or Add a photo or ....
Maybe it would be better to add this as an access control Permission or maybe as part of the modules settings since it a usability and interface setting. I just think this should not be a root user only function as it makes adding content a lot easier.
I think the only complication is that you would need to build the menu off the Permission. So if a user can only create acidfree photos then only the Add a photo link should appear.
Comments
Comment #1
NaX commentedOk I have had looked into this a bit more.
Correct me if I am wrong.
Location: class_album.inc; Function theme_acidfree_print_full_album();
Line 139 the variable $show_box is being created using node_access('update', $node), and I am not sure but this means that the menu box will only show if the user is the owner.
As a temporary fix I set $show_box = 1; Then if a user can upload photos into that album then the menu box comes up with the link Add a photo.
This makes more since to me. As it is now the user has to be root or the owner to have this menu display. Now if the user has the appropriate permissions then they would be able to access the menu. Witch in my opinion make more sense from a usability stand point.
As it stands now works great if there is only one person creating acidfree content. But what if you had many users.
I think that with the Tabs it makes more sense to need to be the owner. [album contents].
The way I did it is not very clean, but you get the idea.
Comment #2
NaX commentedI don't like to duplicate feature request and I always search before posting but it seems this time I did not search hard enough.
I think this feature request is related to my feature request.
http://drupal.org/node/34372
Comment #3
vhmauery commentedI think this is the same issue. I will mark this one as a duplicate.