Closed (fixed)
Project:
Node Gallery Access
Version:
6.x-3.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Jul 2011 at 12:50 UTC
Updated:
27 Aug 2011 at 02:11 UTC
Is there a way to control access to a gallery by role?
Gallery A visible to roles X and Y.
Gallery B visible to roles Y and Z.
The ideal would be to select the roles when creating or editing a gallery.
If not, would it be practical to work on extending this module or should I start somewhere else?
Comments
Comment #1
justintime commentedNode Gallery Access will be able to do this, but can't just yet. The idea is that it will leverage another access module, such as Content Access. When you tell Content Access to limit access to a gallery node, it will inherit down to the individual images.
I have most of it working, but a few major bugs to work out yet. I have been so busy between work and NG3 that I haven't had much time to work on it. It's quickly gaining on my priority list, as NG3 is appearing to be stable.
Note however that you flagged this as a version 2 issue. No work will be done on the 2.x branch to support this.
I'm moving this issue over to the NGA queue.
Comment #2
peterx commentedNG3, Plupload HTML5, Content Access, and Rules should cover all my requirements for access, uploading, and assigning editors to review uploads. My timeframe for the first gallery is a month and it will have limited images I can temporarily control with Content Access. Your NG3 inheritance will be perfect when I start uploading hundreds of images into many galleries.
Some images will be in multiple galleries. I have not looked at this aspect of NG. An image might have two different uses with different access. A picture might show flowers in a park. The image might be in one node with a description of the flowers and in another node with a description of the park. Each node could be used in several galleries with different access controls for each gallery. The workflow might be to upload the image through a contributor role and enter all the image ownership/locations in the node. Editors can then add the node to their galleries. An editor could also attach the image to a different node with a different description. The second node could go in multiple galleries again inheriting the access of the gallery.
Comment #3
justintime commentedI just pushed up a huge commit that works for me in all my tests. See #1247098: How to use Node Gallery Access, and please report any successes or failures. This is essentially a complete rewrite of the module.
Comment #4
peterx commentedGood job. I pushed my gallery site up to Drupal 7.7 as soon as 7.7 arrived and cannot run the test. The change will help some other gallery site owners.
Comment #5
justintime commentedCan I ask what module recipe you used for your galleries on D7?
Comment #6
peterx commentedThe galleries are switched off. Some other module and site conversions are a higher priority. The galleries will be recreated after everything else is fixed. There will be a node per original file then a node per each derived image. Planning has not progressed beyond that.