Gallery3:Season of Usability 2009 Survey, Permissions explanation - Gallery Codex
Personal tools

Gallery3:Season of Usability 2009 Survey, Permissions explanation

From Gallery Codex

Return to survey results main
17: Permissions follow up
Element started 730 Participants
Element finished 710 Participants
Drop-Out 2%
Time to finish 2:22 min (s=5,51 min)
Free Answer

Question 17. If you selected "other" above or would like to be able to utilize permissions to share photos in a different way, please tell us about it here:
Number of valid answers 75

  • With Gallery2 it's too laborious to start limiting permissions.
  • It would be nice to restrict options based on a list of IP addresses or MAC addresses. :)
  • I Restrict Gallery to Members Only
  • htaccess
  • I disallow guest access
  • I find it very ironic that this usability survey could really use some help from someone who knows that requiring JavaScript is poor usability. Also "unknown" was my answer to how many people I share photos with, but the poor usability of this survey didn't allow me to say that.
  • I use Gallery 1. It would be great to be able to share private galleries with family members more easily - without accounts. Accounts (at least in G1) are too cumbersome for computer novices.
  • I only let visitors view resized and watermarked images.
  • Some albums/photos will have different permissions for different groups including who can view, what size they can view, whether they can print, etc...
  • I use gallery to display images of art and other items, not to display "photographs" for their own merit.
  • Individual member controlled folders, as well as group folders.
  • All albums/photos viewable by all my registered users only
  • I restrict access at the album level
  • Unlimited viewing. Restricted uploads.
  • I use basic http authentication for the entire gallery site.
  • integrate with drupal
  • I have folders viewable to everyone; folders viewable to registered users; folders viewable to specific groups of users;
  • I mainly use Gallery as an embedded system within Drupal.
  • Q. 15. Currently use gallery for non-professional, not for profit site that is no longer personal however this does not make it professional however.. Free as in beer :P User can create own albums - sub albums and have moderators.
  • Use the API to handle Facebook Logins and it'll rock.
  • my site is locked via username/password authentication using cookies. once in, a user can view the pictures in my site with no restrictions. No editing permissions are given. The cookie expires after 4 months unless the user revisits my site within that time, in which case, the cookie renews for 4 months.
  • Allow users to create and edit their own albums. - maybe users I authorise for this. Already done this w G2
  • Public albums that general public can view only.
  • Except for the splash page and an email form, the access to my whole personal website (gallery2 + wordpress blog) is password protected. Once logged in, all users can view the gallery pictures, but only registered users can upload their pictures in the gallery.
  • I currently have two installs of Gallery2.3, my live site is completely open to all anon users; my new site is drupal integrated and I am designing it so that users can contribute photos into my galleries, but with a quota system enforced.
  • registred users and not registred users advantage for registred users - see more pics and albums
  • two galleries I use is htaccess-protected for the members of an organisation (shared-password-based) or a working group (ip-range-based), respectively
  • I have a mix of private albums protected by a password that is known to basically all friends and aquaintences. Then I have albums only for family members, and then I have albums that are public to everyone. So three different categories.
  • I do use password protected albums, in addition to hidden albums.
  • I have certain password-protected/hidden album which I share with a particular group. The group does NOT have an account (considered public)
  • I would like better group management, so I can more effectively manage permissions. This is extremely important in how I use Gallery.
  • I have a password for the whole gallery
  • I have restricted ability to view certain albums by IP address/DNS name (using .htaccess since gallery doesn't do it intrinsically).
  • I'd like to be able to specify a copyright license (e.g., Creative Commons) and apply that, rather than using software-based permissions.
  • All pictures are "view-only"
  • All my albums are public - can be seen by anyone
  • I give others the permission to create own albums.
  • I have a section where family members can add their photoalbums and can set permissions who should see it, but as the admin I can see all albums and photos all the time
  • I use permission to have some pictures public and some private. Pictures containing friends/family mainly private. Scenic pictures public.
  • My server contains full size and quality photo directly from my camera. I would like to allow people to purchase for download images from my server that are dynamically resized to their needs from the original image. The different resolutions would have an associated price for each size.
  • I have a group of users on the site (almost all users) who have the ability to create subalbums for their photos. They have full permissions within their subalbums. I maintain the parent structure (by year and season e.g. "2009/Summer 2009") to provide places for users to create sub-albums. I also have a few albums that only I can view.
  • I believe in per-album permissions settings, but not individual photo settings - they should be inherited by the album.
  • Be able to disable anonymous viewing per album.
  • Only registered users can view albums, people can make albums private if needed.
  • I'd like to be able to share private photos in a passwordless way. A password is good for giving access to your private galleries to friends or family; but sometime one would want to share and album with other people like 'not so close" friends or friends of friends without giving them the private part password and without setting an on purpose password.
  • using watermarks
  • I make some photos publicly accessible while leaving the album itself restricted to logged-in users. Then I will embed those publically-available photos into a blog or other post allowing those items to be seen individually, but without giving away access to the entire album. I also link/copy specific items from a private album into a public "highlights" album.
  • For me, it's always important that it is easy to get to the actual source file (so that it says .../pic.jpg in the address bar) as long as you have permission.
  • ability to add group permissions BUT not allow one or two people from that group to view the sub album/photo, etc. - basically, allow for some more advanced boolean permission settings between groups and individual users for a given album/photo, etc.
  • My entire site is private. I have one shared user name and password I give out to family and some friends that lets them view-only the entire site with restricted actions. I use the administrator account to add and maintain.
  • Each user has their own album which they can upload to
  • Creative Commons, Attrib-Non-Commercial-No-derivative
  • I create special permission on single photo for certain group. In a single album some people can view a photo and someone else can not do it
  • Depending on the images is how I manage my image permissions.
  • Permissions is too complex and slow setting up in g2
  • Users -> Groups -> ACLs. 1 ACL should consist of 1 or more Groups (not standalone users). One might want to change the people allowed to view / change / access an album / photo / etc, without messing up the existing groups. Albums + ACLs = Good access control.
  • In addition to collections where access is completely open, and collections which only specific people can access, I have some collections which are reachable by anyone, but the images cannot be found casually by browsing or via search engines. The only way people can get to them is if I (or someone else) sends them links.
  • My gallery is embedded in Drupal. I have a "family" role which I assign to trusted individuals. Members of this group can create their own albums and add photos. They can also comment on other members' photos, but cannot modify an album or photo. I also have a "friend" role whose member can view albums and photos but not post comments. (In the past I had the "guest" role do this, but later closed the site to all but members.
  • I just upload the photos, I am the only user, and the world can do anything else besides administration and uploading
  • I would like to have 1 website gallery with multiple access layers that show customized content to: 1. Anonymous visitors 2. Logged in visitors 3. Privileged visitors 4. Customers 5. Administrators
  • photo's are uploaded by 1 of 3 people. All images of our pulic events we sell so they are watermarked. Internal events are unwatermarked for club members. Public can view all images.
  • I also limit and control what sites may hotlink photos.
  • Password protect the directory where Gallery3 is installed.
  • I create one password protected album for each event, so only the people who had assisted to that event can enter that album.
  • We share our Gallery database with those that are in our network. Photographers upload and have permission to delete and edit.
  • I would like a to have permissions set via virtual host, i.e main website: example.com with albums accessable via: client1.example.com family.example.com friends.example.com with permissions set depending on the virtual host. (prob more apache than anything else)
  • Gallery has got limits in mass editing photo permissions. I usually set the permissions to my photos in the SQL tool where I edit AccessSubscriberMap table directly. It would be really great if there is a new feature for mass photo permissions setting as for photo descriptions editing exists already.
  • On some sites I have integrated G2 with Wordpress through the WPG2 plugin. New user accounts are synched by that plugin. Access level to albums is determined by group membership.
  • Creative Commons License to share with authorization and acknowledgement.
  • Create an .htaccess file to restrict albums to my local network
  • It's my own site, so not many people are going to find there way to it. So I don't worry too much.
  • I would like to utilize more security options, but at present people with ID's get full access, and anonymous people can view everything. "Default settings" in other words. Some other day... not the most important thing to cross off the to-do list.
  • Used to upload images to gallery on my own machine but now mostly copy a few photos to a folder on my webserver and share the url, which may not last long. Not other permission control as such.
  • My gallery album was integrated into drupal. I had user only albums , and public albums , for each user . I used gallery2 permissions set in root gallery albums of public and member only groups based on drupal groups, set so anon could only access public albums and view all sizes , and members able to create albums etc and view all sizes for all albums. Err sort of . The permissions set up was quite intricate and involved, but based on groups . Groups in gallery were same as drupal groups.
  • I have special albums with password but no user limitation.


Return to survey results main