Folder permission problem

check your system and php umask... this can be forced outside of mkdir...

I also ran into problems with the suPHP umask defaulting to 0077.
Setting umask to "0002" in suphp.conf did the trick for me.

I ran into the same issue, and as changing the server's umask wasn't an option, I patched the module so it does a chmod() just after the directory is created, see attached patch.

I'm having problems too with imagecache folder permissions. In my case they are created with 744 and your patch doesn't help.

I've checked a lot of posts about this issue and I think I'm getting mad.

Kind regards.

...and still doesn't work with last update 2.5.

In a server with:

• PHP 5.2.5-pl1-gentoo
• Webserver Apache/2.0.59 (Unix) mod_ssl/2.0.59 OpenSSL/0.9.8g

Where should I change the umask setting? I don't konw almost anything about web servers.

Kind regards.

@Macarro: If you are using suPHP, find the umask in your suphp.conf file. If you are using mod_php, I believe it inherits the umask from Apache, which typically inherits the system umask. If you don't want to change your system umask you can edit the Apache init script and set it there using the umask command. There may be other ways to do it depending on your setup, but you're probably going to have to do some digging to find out what they are.

Hi

I've solved the problem patching the module but I don't know yet where is the problem.

In my site folder/file creation works perfectly for other modules and I've also created text files from my own php code simply saving a new file and they appear with the right permissions. So I assume it's not a server configuration error or problem (just an assumption).

My server admin told me the I'm working on a virtual apache server without any umask restriction. So, to check it I simply print the umask with "print umask()"... and I got 27 as result... So there was the problem. I don't know almost anything about this kind of issues but if this was right I would be impossible to get 705 permissions and that's not my case.

This way the simply solution was to modify the module (2.5 version) about at line 463 to force umask(0) during folder creation:

...
  $oldmask = umask(0);
  
  if (!file_check_directory($dir) && !mkdir($dir, 0755, true)) {
    watchdog('imagecache', t('Failed to create imagecache directory: %dir', array('%dir' => $dir)), WATCHDOG_ERROR);
    return false;
  }
  umask($oldmask);
...

Maybe I should put umask modification inside the if loop for security reasons... I don't know.

Kind regards and thanks for your answer, adamo.

If modifying the module is the solution, it would be better to call chmod() after the file is created than to use umask(). From the PHP manual:

Note: Avoid using this function in multithreaded webservers. It is better to change the file permissions with chmod() after creating the file. Using umask() can lead to unexpected behavior of concurrently running scripts and the webserver itself because they all use the same umask.

http://us.php.net/manual/en/function.umask.php

Thanks for the note, adamo.

I think I tried it and it didn't work in my case. Anyway I have to check it, I'll put here my results.

subscribe

Just in case it helps, I've recently upgraded to Drupal 6 and Imagecache works perfectly now, there is no folder permissions problem.