somewhat related to the previous feature request regarding thickbox compatibility. the hacks to the JS file to allow thickbox to work for a customer is working, but I have an anomaly in that, if Drupal is set to private in the file system configuration, and you are logged in, you are able to view the image properly, but not if you are anonymous. An example url would be http://www.domain.com/systems/files/option-images/image1.jpg. If image1.jpg was an option image on an item, I would be able to view the image properly via that url if I was logged in, but not if I log out and attempt to view the same url. The resulting http error code is a 403 forbidden.

I've been looking at the code and I can't seem to find anything that would prevent it for anonymous users but not authenticated users.

granville

Comments

tjholowaychuk’s picture

tjholowaychuk commented
Status: Active » Postponed (maintainer needs more info)

That is the nature of the private file system, not the module itself. I dont think I fully understand the issue though, if you have it set to private, why would you want the images to be public? I am not overly knowledgeable about the current private filesystem implementation so I cannot say for sure but if you would want ONLY images to be public then perhaps they can be saved to a different directory without being piped through Drupal for the user_access check

graper’s picture

graper commented

From what I understand, Drupal's Public file system setting means that links made from the drupal api to files will be made so that the files are server directly from the server's file system. Example: http://www.domain.com/diretory/filename.ext. Setting drupal's file system to private just means that the files are delivered via code through Drupal in which permissions can be used to determine the accessibility of files. example:http://www.domain.com/system/filename.ext which would make drupal check for permission for accessing the file before serving up the file.

The permission section has "view option images" for this module and I have anonymous checked, but when set to private anonymous users are not able to see the option images.

FYI, I did make some changes to the js code and it could be my changes, but I thought I would turn this in for further investigations as all I did was change the target that the js code uses and some style changes.

Granville

acouch’s picture

acouch commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

The 5.x version is no longer being supported for this module. We are cleaning up the 6.x version and preparing for the 7.x version.