Closed (won't fix)
Project:
Image
Version:
6.x-1.0-alpha3
Component:
image.module
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
20 Dec 2008 at 11:08 UTC
Updated:
27 Feb 2009 at 17:00 UTC
I have a problem with displaying image to Anonymous users, I have check all the access rules in regards to content and still this problem is there, when over looking the browser source the image is not attached, but when logged in the image codes are attached making it possible to view the images.
does this sound like a general which can be sorted out quit simply or do I have to add another module to this one?
Regards
Dan
Comments
Comment #1
dsp1 commentedI am having the same issue.
I am using image 5.x-1.9 and drupal 5.14,php 5.2.5
the issue seems to occur when you attach image to a node like blog. The image node is set to Not Published.
Which I want it that way, but only authenticated users are able to see the images.
I have "view original images" access control checked for both anonymous and authenticated.
think-in, if you are not a developer for the image module, you should not enter yourself into Assigned.
Comment #2
dsp1 commentedComment #3
dsp1 commentedbump
Comment #4
dsp1 commentedI have done more research.
I have found that the original authenticated user can view the image and the site admin and root user can view the image.
Anonymous, authenticated, user admin users cannot view the images.
It is strange that Site Admin and User Admin have the same Access Control settings for the image module.
Other modules access control are different for the Site Admin and User Admin.
what I have checked for site admin that user admin does not have checked is: use PHP for block visibility, administer filters, administer gallery settings, administer locales, administer menu, administer content types, administer nodes, administer pathauto, access administration pages, administer site configuration, select different theme, access all views, administer views.
does anyone know what other core or contributed modules might interfere with image module display for certain users?
Comment #5
advseb commentedsubscribe, problem also exists in 6.x-1.0-alpha3
Comment #6
dsp1 commentedI checked my Content Types workflow and Image does not have published checked.
Not sure if updating previous Image versions affected this or I changed it.
Now I know why the image files are not being published.
But, why is the display of images not consistent?
I would like unpublished images viewable in the content of other nodes for all user accounts, not just root and site admin.
any way to do this?
can anyone shed light on what is going on with image display?
Comment #7
sunUnpublished content is never accessible in Drupal. This was always the case and if Image behaved differently before, that was a big bug (a.k.a. security issue).
Comment #8
advseb commentedI'm sure this is not fixed. Even if the content is published, it is only accessible to those who have the same role as the publisher. This doesn't make sense, because the image is embedded in a page and should therefore have the access rights set as the page.
Comment #9
advseb commentedComment #10
Josie_h commentedI have a 'related' problem in as much as I disable the 'view original image' option (both auth & anon) and the originals are still displayed with a derivative is clicked.
Can anyone tell me how this issue was fixed as I might be able to find a connection/fix for my problem.
Thanks.
Comment #11
adub commentedSame problem here in 6.x-1.0-alpha3 for published images.
Comment #12
sunFirst of all, 5.x-1.x was a different piece of software than 5.x-2.x and 6.x-1.x now is. The original poster's issue is most probably a completely different issue (as explained in #7).
Anyway, please provide a list of all other contrib modules you have installed, especially modules that deal with node access permissions, like Organic Groups, Content Access, etc.
While doing so, please also try whether disabling all other contrib modules and hitting the "Rebuild node access permissions" button on admin/content/node-settings helps.
Comment #13
sunSorry, without further information this issue can only be marked as won't fix. Feel free to re-open this issue if you want to provide further information.