furrychops Posted January 23, 2007 Posted January 23, 2007 I am in the beginning stages of configuring my osCommerce webstore, and the pink error bar on top says "Warning: I am able to write to the configuration file: ' . dirname($HTTP_SERVER_VARS['SCRIPT_FILENAME']) . '/includes/configure.php. This is a potential security risk - please set the right user permissions on this file." How do I resolve this? Also, how do I make it so that when an eventual customer shops at my webstore, that they don't see the pink error bar? THANK YOU!! :) Jeremy
Rachael w. Posted January 24, 2007 Posted January 24, 2007 Looks like your permissions are wrong on your includes/configure.php file. I believe they need to be set to 644 for both the catalog/includes and admin/includes configure.php files.
furrychops Posted January 24, 2007 Author Posted January 24, 2007 I tried changing the permissions to the configure.php files to 644 and i am still getting that pink error bar at the top. do you know of anything else i might try? Thank you so much! Jeremy
satish Posted January 24, 2007 Posted January 24, 2007 I tried changing the permissions to the configure.php files to 644 and i am still getting that pink error bar at the top. do you know of anything else i might try? Thank you so much! Jeremy set permission as 444 Cheers!! Satish Ask/Skype for Free osCommerce value addon/SEO suggestion tips for your site. Check My About US For who am I and what My company does.
furrychops Posted January 24, 2007 Author Posted January 24, 2007 I set the catalog/includes/configure.php to 444 and the admin/includes/configure.php to 444. The result is that I still have the same pink bar at the top of the screen with the same error message: Warning: I am able to write to the configuration file: /home/users/web/b2335/pow.metropolisonline/htdocs/shop/includes/configure.php. This is a potential security risk - please set the right user permissions on this file. Any other suggestions? Thank you both so far for your help! Jeremy
furrychops Posted January 24, 2007 Author Posted January 24, 2007 Wait a minute. I still hadn't changed permissions on the root includes folder version of configure.php. I just changed the permissions on that one, and lo and behold - the error message is gone. Thank you! Jeremy
Recommended Posts
Archived
This topic is now archived and is closed to further replies.