RE: Drupal 6 File Permissions

Hi-

Chocolate bars may worsen the crisis. Try some deep breathing.

I believe most file settings can be set at 644 and the owner should be
www-data or apache.

You can set permissions recursively for all sub-directories.

chown -R www-data:www-data directory

chmod -R 644 directory

I am typing these from memory so you might want to Google it.

Try making sure the owner is set correctly before you start changing the
read write permissions.

I use Teraterm and have found it much more speech friendly.

 

 

H.R. Soltani

 

 

From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James
Sent: Wednesday, March 16, 2011 2:14 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: Drupal 6 File Permissions

 

Hi,

I'm hoping this won't be a long process, but Oh well if it is. I didn't
understand what would happen when I dumped my installation onto a Linux
server with file permissions. I need to find the documentation that tells
the optimal file permissions to set for the Drupal site, and I need to
change the owner to Apache, or at least I think I do, rather than me. So
far, I'm unhappy with my setup on my Windows box. I have NVDA and Putty, but
I can't hear the characters I type. I have JAWS, but when content scrolls
past the bottom of the screen, it speaks the whole screen. I tried to
install Cygwin, but failed to get it working. Right now, I'm under a
deadline and very frustrated. So now that I've ranted a while, what do I do
once I've ingested a few chocolate bars to calm down?

 

Thanks.

 

Jim

 

  _____  

This e-mail and any attachments to it are confidential and are intended
solely for use of the individual or entity to whom they are addressed. If
you have received this e-mail in error, please notify the sender immediately
and then delete it. If you are not the intended recipient, you must not
keep, use, disclose, copy or distribute this e-mail without the author's
prior permission. The views expressed in this e-mail message do not
necessarily represent the views of Highmark Inc., its subsidiaries, or
affiliates.

Other related posts: