Jump to:
| Project: | Node Gallery |
| Version: | 6.x-2.0-alpha10 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I've installed Node Gallery, and when creating my very first gallery, I set the image type to Image. I gave appropriate permissions to a user, who can now look at the (empty) gallery page. However, if that user clicks on Upload Some!, the result is Access Denied.
I believe the reason is that the Image module has chosen to use "create images" as the name of their permission for creating images, while the node_gallery_use_access function assumes that the permission name is always "create $image_type content". Granted that's a ubiquitous convention, but as far as I know, it's not a documented requirement.
I have to use the Image type, because I'm using the Image Browser module to hook into FCKeditor for uploading images. My goal is it that when a user uploads an image from within FCKeditor, to use as part of a post (e.g. blog entry), the image also becomes part of that user's gallery. The Image Browser module hard-wires the uploaded node type to be Image, so I have no choice in the matter (until I can find a comparable module that integrates with a WYSIWYG editor).
I don't think there's any currently reliable way for Node Gallery to determine whether the user has permission to create a new node of the given type for the gallery other than actually trying to create the node. The current approach will work most of the time, but not all the time. I could certainly go along with Drupal imposing a naming convention on permissions, but for now, why bother? There's no security issue around displaying the upload page, even if the user doesn't have upload permissions. I appreciate the usability value, but not if it can't be made to work correctly, and I hesitate to suggest treating the Image content type as a special case.
Comments
#1
Node Gallery is not designed to work with the image.module
#2
If you change your workflow, Node Gallery can work nicely.
For example, I require my users to upload into their gallery first. After the pics are in the gallery, they can use the server browse button from IMCE (on the FCKeditor Insert Image dialog) to browse their gallery folders to link to their pics. If you want them to use a particular size of pic, you can set Image Cache accordingly and the setup IMCE to allow the user's Image Cache folders to be accessible to the user. IMCE will allow you to define what folders are accessible to users.
IMCE works nicely with FCKeditor and Node Gallery.
#3
@kmonty
That's it? Simply "not designed to work with"? "Won't fix"? Why not?
Isn't the Images module one of the most used and integrated modules? Shouldn't modules and developers be compatible, work together? Why does it sometimes seem that there is competition going on within Drupal instead of collaboration? Is that optimizing resources, making life easier for the drupal community?
Anyway node_gallery has some additional options that are magnificent, specially the option to make a Gallery part of the node. Image gallery has other great options too, like batch upload and independent gallery management. Is it too much asked to have the two work together or do we have to choose between one and the other? Does a website that has started out with the Image module and has hundreds of images and a great number of galleries have to be fully restructured just to be able to use those pictures under Node-Gallery?
I'm a newbie (even after 2 years of wrestling with drupal) and have lost weeks trying to figure out how to have a gallery within a node (views, CCK, and more but don't recall) until I found Node-Gallery. And now I have to choose whether to forget about it or start over again???
Main question, how can existing images on the server be used with Node-Gallery? I only found the option to upload (a specified number of) new images (not even through batch), but not the possibility to assign existing images to nodes.
I'll try with Tally's workflow suggestion, report later.
#4
@suffering drupal did you manage to do what you mentioned? I also have a lot of old images I should assign to a gallery...
I hope you can give me any tip.
#5
@Mairav
I gave up on Node Gallery after discovering it is not Multilanguage ready; for each new translation you have to upload the pictures again! Stupid not to have checked right away, but of course I was stuck in the other issue - not resolved by the way.
Now I am trying (and suffering) with Gallery Assist. I confirmed it DOES support multiple languages, although now I have a problem with lightboxes....
But as always with Drupal, if only I reach about 70% of my intention I call it a win. Since Multilanguage is more important than lightboxes I'll stick with Gallery Assist.
#6
Node Gallery is not designed to work with the image.module
Can someone please post this clearly on the project page? The fact that any node type can be associated with a gallery is misleading.
#7
@suffering drupal
I'm in the same sinking boat as you. Did you find a workaround?