A question about the images directory created by the image module and nested in the files directory:

I don't know if this is related to the problems I'm having trying to get the module to run but I am unable to view the contents of the images directory.

I'm planning on using the photo gallery to archive all of the photos for my volunteer group. I don't want these photos to be hidden in some directory that I cannot open. So is it normal that access to the images directory is forbidden or is it broken? If the former, is there a different module that I can use to create a photo gallery that also allows direct access to the directory?




Emiliano’s picture

Hello Sue!

I faced a similar problem and found some discussion about this here: http://drupal.org/node/10658

and here: http://drupal.org/node/23535

Now I create the files, tmp and image directories prior to everything else. ;-)

And don't be upset at this. You'll see Drupal is amazingly good!


sepeck’s picture

If you don't create the image directories first, then the image module does so for you. The image module can only do this with the account that is configured to run the web server. If permissions in that directory for the web server acocunt are set so that directories are owned by the server and deny access to everyone else, then your best bet is to create these directories yourself first.

This is a server configuration issue more then it is a Drupal issue.

Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
Test site, always start with a test site.
Drupal Best Practices Guide

sjmagain’s picture

Thanks, everyone. I can now open the images and nested temp directories. Unfortunately, both remain empty which confirms that the image module I installed yesterday is not working properly.