chrometweaks.org

What's your favorite web iPage hosting service?

Click Here To View All Answers...


Got a quick question: What's your favorite web iPage hosting service? Looking forward for any comment. My 2nd question... I'm getting this error on my OSC main page:.

Warning: I am able to write to the configuration file: /home/visolu2/public_html/shop/includes/configure.php. This is a potential security risk - please set the right user permissions on this file..

I checked this file and and did chmod, but the message persists..

Any ideas?..

Comments (88)

I'm stumped. I'm not so sure what is the answer to that question. I'll do some research in Google and get back to you if I find an decent answer. You should email the people at iPage as they probably could give you help..

Comment #1

It was 644 already, and I changed it to 444, but the message was still there, so I changed it back to 644, and the message is still there..

It was working fine before, but I had to re-install my OSC and this message started to appear after the re-installation...

Comment #2

I got the same error today also, although I had not changed or loaded anything on my iPage site since last time I looked at my homepage (and it was fine then)The configure.php file was set at 644. I changed it to 444 and the error went away. But it is very strange. I think it may have something to do with changes made by my iPage site host this weekend, but I am not sure. Hope it is not opening up unseen holes in security. Makes me paranoid...

Comment #3

UPDATE: found an osCommerce Knowledge Base article that helps....

Able to Write to the Configuration File..

Comment #4

Hi Paul,.

I too suspect that my webhost did something that introduced the error. My webhost is lunarpages, btw..

I looked at that link to the KB, but I'm confused. The article tells you to do:.

Chmod 777 /path/to/osCommerce/includes/configure.php.

Why would you set it to 777? Isn't that even more unsecure than 644?.

Doesn't make sense...

Comment #5

Yeah, I just assumed it was a typo and it meant 744 or something less. I cannot imagine why 444 didn't work for you. Of course 644 is not working on lp for me either, only 444, which is a small blessing I guess. I may email support about it, because I've probably forgotten to set something else correctly .....

Whatever has changed on the box I'm on at LP (maybe SuPHP) is still giving me fits mostly it was my fault at first for not changing every 777 to 755 or less (stupid me loaded up pics and forgot to chmod them). Now that's all fixed (mostly), but another problem arose cart empties itself anytime customer clicks on "Home", and, half the time when customer clicks on "continue shopping" it takes them back to the previous product's page rather than the overall products page. I tried to replace the shopping_cart.php with a backup and that didn't work, plus it brought up the dreaded "page link!" error..

If I find any help at all that may help you also, I will post it here...

Comment #6

Think I found my cart clearing error my homepage currently immediately redirects visitor to cart folder, so I guess it starts a new session or whatever on the redirection command... or something like that? So luckily it seems to have nothing to do with the LP changes or chmod stuff..

I thnk half of what confuses me is similarly or same named files in different directories of OSCommerce ... being new, I probably need to find and read some hierarchy faqs or knowledge base articles to get the flow of things..

Comment #7

Hey Paul,.

I changed it to 444 and it worked. It wasn't working before because I made a stupid mistake..

The Admin folder also has an "includes" folder, similar to the one on the root folder, but everything in it is related to the admin section. Hope that helps a bit...

Comment #8

I'm getting this error on my OSC main page:.

Warning: I am able to write to the configuration file: /home/visolu2/public_html/shop/includes/configure.php. This is a potential security risk - please set the right user permissions on this file..

I checked this file and and did chmod, but the message persists..

Any ideas?..

Comment #9

What did you chmod the file settings to? they need to be 644 at a minimum..

Comment #10


This question was taken from a support group/message board and re-posted here so others can learn from it.