edwuh Posted January 12, 2005 Share Posted January 12, 2005 Hello I have just installed osCommerce and can not get rid of the message which reads: Warning: I am able to write to the configuration file: /home/www/webdiner.bz/test/catalog/includes/configure.php. This is a potential security risk - please set the right user permissions on this file. Any help would be greatly appreciated Link to comment Share on other sites More sharing options...
Guest Posted January 12, 2005 Share Posted January 12, 2005 the knowledge base hass answers. anyway set the properties on your catalog/includes/configure.php file to 644 via the host cpanel file manager Link to comment Share on other sites More sharing options...
edwuh Posted January 12, 2005 Author Share Posted January 12, 2005 the knowledge base hass answers. anyway set the properties on your catalog/includes/configure.php file to 644 via the host cpanel file manager <{POST_SNAPBACK}> I am using WS_FTP and when I right click on the file and change the properties to 644 nothing happens. I have looked throught he knowledge base and have not found anything yet. Thanks for your suggestion and I will keep looking. Link to comment Share on other sites More sharing options...
Guest Posted January 12, 2005 Share Posted January 12, 2005 ws_ftp usually doesnt work too wel. try your host cpanel/vdeck Link to comment Share on other sites More sharing options...
edwuh Posted January 12, 2005 Author Share Posted January 12, 2005 To my knowledge my hosting company does not have "cpanel/vdeck", but I will check into it. Thanks for your help! Link to comment Share on other sites More sharing options...
edwuh Posted January 12, 2005 Author Share Posted January 12, 2005 I have checked with my hosting and confirmed that they do not have "cpanel" or "vdeck". Additionally they confirmed that the permissions were set to 644 on the /catalog/configure.php script and should not be receiving the error. I have also looked through the Knowledge Base with no success. Any thoughts or ideas on how I may resolve this? So far I love the look and feel of this program and would like to continue using it but I really need to have that error message gone. Any help is greatly appreciated Link to comment Share on other sites More sharing options...
Guest Posted January 12, 2005 Share Posted January 12, 2005 U know what? there are THREE config files u must set. /catalog/includes/configure.php is the one i had to set to get that error to go away. There's also one in the admin folder. Set all of em... Link to comment Share on other sites More sharing options...
edwuh Posted January 12, 2005 Author Share Posted January 12, 2005 Thanks for the tip! I only found two files named configure.php, one in catalog/includes and one in catalog/admin/includes and changed them both...still nothing! I will keep looking for the third and if you have any other suggestions I will be grateful? I am very close to scrapping this whole thing! Link to comment Share on other sites More sharing options...
♥Vger Posted January 12, 2005 Share Posted January 12, 2005 Look to see if you have a folder called 'local' with an alternative configure.php file in there. If it exists it has the ability to supercede your includes/configure.php file and application_top.php. Vger Link to comment Share on other sites More sharing options...
dentonio69 Posted January 13, 2005 Share Posted January 13, 2005 I thought the permission had to be set to 444 and that 644 was the one that gives the error? Link to comment Share on other sites More sharing options...
♥Vger Posted January 13, 2005 Share Posted January 13, 2005 644 gives the owner read and write permissions - so the file is still writable (if only by you). Set the includes/configure.php to 400 (Owner - Read Only). You can set the permissions for admin/includes/configure.php to either 644 or 400 (up to you on that file). Vger Link to comment Share on other sites More sharing options...
edwuh Posted January 13, 2005 Author Share Posted January 13, 2005 I thought the permission had to be set to 444 and that 644 was the one that gives the error? <{POST_SNAPBACK}> Yep, That did the trick! When I set the permissions to 444 the message went away! Thanks everybody for your help. Link to comment Share on other sites More sharing options...
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.