Why does the Drupal installlation directory have to be writable in order to use this software? I can't get this to happen, so I've tried pointing to a different directory that I can chmod 777. However, the script still complains that the installation directory is not writable, even though the new folder is listed, and is outside the installation directory. Any chance a future version won't have this requirement?

Comments

Anonymous’s picture

Anonymous (not verified) commented

Same here - I cannot chmod the Drupal directory to 777. Why is it not possible to just have the designated backup directory set to 777 instead?

cyprien2’s picture

cyprien2 commented
Version: 5.x-2.x-dev » 5.x-4.x-dev

Same here too... We are doing something wrong ?

jenscbc’s picture

jenscbc commented

I agree, it would be nice if it were possible to have the backup dir outside the web servers scope. I get the same error. I am able to change my drupal installation directory, but I'm afraid of the security risks it might pose to have a backup of my database inside the web servers scope.
It would be very useful if the module could handle the situation with external backup dir.
Thanks!