Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Config File Permissions


gottahave

Recommended Posts

Posted

Having problem changing file permission on includes/config file. After changing permission and saving, the permission reverts to the previous setting.

 

Any advice appreciated.

 

Neil

Posted

Neil,

 

If you currently have the file permissions set at 444, you can not overwrite the file, you will have to rename the file on the server (configure_old.php) and then upload the edited file. Remember to again change the permissions on the edited file to 444.

 

 

Chris

Posted

Try to change the permission via your host cpanel

 

I've been doing it via Filezilla so I'll try your suggestion.

 

Many Thamks

 

Neil

Posted

Neil,

 

If you currently have the file permissions set at 444, you can not overwrite the file, you will have to rename the file on the server (configure_old.php) and then upload the edited file. Remember to again change the permissions on the edited file to 444.

 

 

Chris

Thanks Chris - I'll try that too.

 

Neil

Posted

If you currently have the file permissions set at 444, you can not overwrite the file, you will have to rename the file on the server (configure_old.php) and then upload the edited file.

Easier: change permissions to 644 before editing or uploading a replacement copy, and then change them back to 444 (if necessary to silence the warning message). It's likely that you will not be able to rename the file (per DunWeb's instructions) anyway while it is 444, so you'll need to change it to 644 anyway.

 

And yes, many servers are configured to silently ignore requests from FTP to change permissions. You need to use your host's control panel (e.g., cPanel).

Posted

The above is the likely solution .. however I do have a client who uploads EVERYTHING as root.

 

This would also create this issue.

Posted

I do have a client who uploads EVERYTHING as root.

Anyone who installs an application such as osC as "root" is a moron, and deserves to have all sorts of bad things happen to them! "root", for the edification of newbies, is the "superuser" ("God account") and should only be used for the highest level work when absolute powers are absolutely necessary. For everything else, use a normal user account. When something goes haywire or gets hacked, the bad code won't have super powers and you won't have a bad guy running as "root", with all those powers. Just the one application, at worst, will get mangled.

Posted

Anyone who installs an application such as osC as "root" is a moron, and deserves to have all sorts of bad things happen to them! "root", for the edification of newbies, is the "superuser" ("God account") and should only be used for the highest level work when absolute powers are absolutely necessary. For everything else, use a normal user account. When something goes haywire or gets hacked, the bad code won't have super powers and you won't have a bad guy running as "root", with all those powers. Just the one application, at worst, will get mangled.

 

Quite .. scary isn't it.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...