Posting in the Magento forums has been disabled pending the implementation of a new and improved forum solution which should better serve the community.

For new questions please post at magento.stackexchange.com, the community-run support site for the Magento community. We will be providing updates on the new forum solution soon. For questions or concerns please email community@magento.com.

Magento Forum

Page 5 of 5
Error: Please check for sufficient write file permissions
 
Coalesce Creative
Jr. Member
 
Total Posts:  16
Joined:  2009-03-03
 

Sindre thanks for your reply. Im just not sure why Magento was built to handle permissions so differently than other opensource packages.

 
Magento Community Magento Community
Magento Community
Magento Community
 
tradiArt
Guru
 
Avatar
Total Posts:  379
Joined:  2008-04-28
 

I’m extremely confused with this issue.

I was in a shared account and everything was going perfect, slow, without innodb, but perfect.

Now I have migrated to a VPS and I’m having this problem. My host has recommended me not to leave all dirs with 777 permissions, which seems logical.

I can’t access magento connect manager now.

SO....

what options do we have now?

Sometimes I wonder why everything in Magento is always so complicated… :-(

 
Magento Community Magento Community
Magento Community
Magento Community
 
fancytricks
Jr. Member
 
Total Posts:  2
Joined:  2009-02-18
New Zealand
 

Ok simple:

1) Public_Html or Magento main folder = 777
2) downloader/config.ini = 666

www.undergrounddesign.com.au

 
Magento Community Magento Community
Magento Community
Magento Community
 
Sindre|ProperHost
Mentor
 
Avatar
Total Posts:  1158
Joined:  2008-04-24
 

XOXO: this is probably because your shared host where running suEXEC/suPHP, which only requires ‘644’ and ‘755’ permissions. On your VPS, PHP is running as an Apache module, which means that PHP scripts are executed under the same user as the Apache process. Therefore you will need ‘777’ permissions on files/directories that must be writable.

 
Magento Community Magento Community
Magento Community
Magento Community
 
tradiArt
Guru
 
Avatar
Total Posts:  379
Joined:  2008-04-28
 

Thank you all for replay,

Seems strange, I’m running two installations, one at root, the live store, and other into a folder, for testing, and this is the store that can’t connect to magento connect.

After asking my host:

Server runs PHP on DSO and Apache suEXEC is enabled.
Default PHP Version (.php files) 5
PHP 5 Handler dso
PHP 4 Handler none
Apache suEXEC on

So what permissions do I need? 755 or 777?

Thank you for your help!

 
Magento Community Magento Community
Magento Community
Magento Community
 
Sindre|ProperHost
Mentor
 
Avatar
Total Posts:  1158
Joined:  2008-04-24
 

DSO means apache module (mod_php), so you will need 777 permissions for any directory that must be writable by Magento and 666 for writable files. suEXEC has no effect on PHP scripts as long as they are handled by DSO. Be careful with these permission settings, as they are not particularly safe. You should atleast reset the permissions when you are done with Magento Connect.

Hope this helps.

 
Magento Community Magento Community
Magento Community
Magento Community
 
tradiArt
Guru
 
Avatar
Total Posts:  379
Joined:  2008-04-28
 

Thank you Sindre,

Well, I can always use SSH, but magento connect is soo nice grin

I will change permissions once finished.

Thank you for your help.

 
Magento Community Magento Community
Magento Community
Magento Community
 
Coalesce Creative
Jr. Member
 
Total Posts:  16
Joined:  2009-03-03
 
fancytricks - 24 March 2009 10:18 PM

Ok simple:

1) Public_Html or Magento main folder = 777
2) downloader/config.ini = 666

www.undergrounddesign.com.au

Fancytricks, that definitely DOES NOT work

 
Magento Community Magento Community
Magento Community
Magento Community
 
Sindre|ProperHost
Mentor
 
Avatar
Total Posts:  1158
Joined:  2008-04-24
 

Coalesce Creative: You need to chmod _every_ folder in your Magento install, including the root folder, to 777 if you want to use Magento Connect and your server is running mod_php. In addition, any files that must be overwritten (e.g. during an upgrade) must be writable (i.e. 666 permissions). It will not suffice to change the perms on only the main folder.

Be careful with these permission settings as they are a huge security risk, especially in a shared hosting environment.

You might want to use PEAR via SSH instead of Magento Connect.

 
Magento Community Magento Community
Magento Community
Magento Community
 
Coalesce Creative
Jr. Member
 
Total Posts:  16
Joined:  2009-03-03
 

Sindre, thank you for your reply. If we switch to suEXEC, suPHP, or phpSuExec this seems like it would make this much more manageable.

However would this greatly affect other PHP scripts we have running on our server? ie. Joomla installs, Wordpress, etc.?

 
Magento Community Magento Community
Magento Community
Magento Community
 
Sindre|ProperHost
Mentor
 
Avatar
Total Posts:  1158
Joined:  2008-04-24
 

The other scripts should not be affected. But please note, suPHP/phpSuExec has a significant performance hit compared to running PHP as an Apache module.

Another thing is that suPHP does not allow world writable files or directories (i.e. permission mode xx7 or xx6). This will generate a 500 internal server error. You should therefore change the permissions on all directories to ‘755’ and all files to ‘644’ if you install suPHP.

 
Magento Community Magento Community
Magento Community
Magento Community
 
fancytricks
Jr. Member
 
Total Posts:  2
Joined:  2009-02-18
New Zealand
 
Coalesce Creative - 26 March 2009 07:55 AM

fancytricks - 24 March 2009 10:18 PM
Ok simple:

1) Public_Html or Magento main folder = 777
2) downloader/config.ini = 666

www.undergrounddesign.com.au

Fancytricks, that definitely DOES NOT work

Yes this is assuming that you have set the rest of the permissions ok though SSH.

find ./ -type d -exec chmod 755 {} \; && find ./ -type f -exec chmod 644 {} \;

 
Magento Community Magento Community
Magento Community
Magento Community
 
smalltom
Jr. Member
 
Total Posts:  10
Joined:  2008-03-23
 

rolleyes My solution:
1, add apache to the group of owner
2, umask 002
3, chmod ug+w -R magento

it seems work

 
Magento Community Magento Community
Magento Community
Magento Community
 
fourroses
Sr. Member
 
Total Posts:  125
Joined:  2009-08-19
 

i just had to change the publichtml folder to 777 and it worked.

 
Magento Community Magento Community
Magento Community
Magento Community
Magento Community
Magento Community
Back to top
Page 5 of 5