Posted by scooper on July 21, 2010 at 1:39am
2 followers
Jump to:
| Project: | Image Gallery Access |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I had Image and Image Gallery functioning properly - 6 galleries display at path /image. Versions are Drupal 6.17, Image Gallery 6.x-1.0-beta5, ACL 6.x-1.0. Image Gallery is a view (by default) in case that matters. I also have Content Access installed 6.x-1.1.
I installed IGA so that I could create a private gallery. I rebuilt permissions as instructed. Next, all my Image Galleries and the Taxonomy terms (gallery names) for Image Galleries were gone. Path /image stated that I had no galleries. There was no oppotunity to set permissions for my galleries because they couldn't be found.
I disabled IGA and the Image Galleries and Taxonomy returned.
Any suggestions?
Comments
#1
Use the non-views galleries.
#2
I found a simpler solution - if I log in as User 1 I can see all the galleries and adjust the permissions between Content Access and IGA, to create public and private galleries.
IGA is now working with the Image Gallery view. I didn't think to try User 1 before because the role I was using "webmaster" has permission to do everything.
#3
Yes, indeed, this was implemented quite a while ago (see #614790: How to make this work on Views).
However, now that you mention the "webmaster" I understand what happened. IGA intends to control not just access to the images and image galleries but also access to the admin/content/image/* pages. This access is provided by the 'administer image galleries' permission, but once you install IGA, IGA's View access is required, too, and that is not provided automatically, so webmasters lose access to all galleries.
The idea here is that IGA should allow you to restrict gallery administrators (who can change access rights if they have access!) to parts of the gallery hierarchy.
I found some bugs in that area which I fixed in the -dev version. However, the original issue remains, and I'm not sure whether and how to implement a solution.
We could, for example, enumerate the roles at installation time and assign View access to all 'administrate image galleries' roles for all galleries. And we could also assign View access by default, when a new gallery is created. This would preserve core's behavior, but it causes problems later on: if we subsequently remove 'administer image galleries' from a role, then that role keeps its View access.
UI-wise I don't want to add another column just for this. I think we can live with View doing double duty for gallery administrators.
#4
Still pending...