Guest Posted April 30, 2006 Posted April 30, 2006 I recently moved all my files up a directory within my hosting account for better indexing by search engines. So instead of the catalog being www.yoursite.com/shop/ it is now at www.yoursite.com. Well I moved everything and I got the message that it is able to write to the file configure.php. I went to change the file permissions to 444 (read for glodal) and it stated it changed (through FTP) but when I refreshed the window, through FTP, it showed it back to 644. I have contacted support with my hosting account and they just have come off as morons and really don't know what I am saying. It seems to me that I may know more than they do about websites. So I have tried everything including another FTP program and trying it through Internet Explorer but it changes back after Refresh. I have also noticed that it is only when I am trying to change the write permissions for Owner/User. Everything else that I change "sticks". Any Ideas?
j_may80 Posted April 30, 2006 Posted April 30, 2006 I had remnants of frontpage extensions floating around. Frontpage makes all your stuff read only. Contact your host, ask them to remove all of the hidden frontpage extension files that aren't always seen by you or me. They say to not even to worry about changing permissions anymore. I don't know about that one. :-" Good luck. :thumbsup:
Guest Posted April 30, 2006 Posted April 30, 2006 I recently moved all my files up a directory within my hosting account for better indexing by search engines. So instead of the catalog being www.yoursite.com/shop/ it is now at www.yoursite.com. Well I moved everything and I got the message that it is able to write to the file configure.php. I went to change the file permissions to 444 (read for glodal) and it stated it changed (through FTP) but when I refreshed the window, through FTP, it showed it back to 644. I have contacted support with my hosting account and they just have come off as morons and really don't know what I am saying. It seems to me that I may know more than they do about websites. So I have tried everything including another FTP program and trying it through Internet Explorer but it changes back after Refresh. I have also noticed that it is only when I am trying to change the write permissions for Owner/User. Everything else that I change "sticks". Any Ideas? I've got the same problem. Until the permission on the configure.php file is set to 444, you'll get the warning on your home page. I can't get it to stick. Maybe there's a script in one of the includes that returns the setting to 644. Before I comb those, though, I'm going to try the advice on FrontPage extensions. It wouldn't surprise me if that's screwing things up. gdane
AlanR Posted April 30, 2006 Posted April 30, 2006 I've got the same problem. Until the permission on the configure.php file is set to 444, you'll get the warning on your home page. I can't get it to stick. Maybe there's a script in one of the includes that returns the setting to 644. Before I comb those, though, I'm going to try the advice on FrontPage extensions. It wouldn't surprise me if that's screwing things up. gdane Try this: http://www.oscommerce.com/forums/index.php?sho...06entry343806 Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)
Guest Posted April 30, 2006 Posted April 30, 2006 I had remnants of frontpage extensions floating around. Frontpage makes all your stuff read only. Contact your host, ask them to remove all of the hidden frontpage extension files that aren't always seen by you or me. They say to not even to worry about changing permissions anymore. I don't know about that one. :-" Good luck. :thumbsup: Removing Frontpage extensions didn't make any difference for me. Still stuck with 644 on configure.php, which means I'm still stuck with that warning at the top of every page on my store. Not worrying about permissions doesn't make sense. Having that warning sucks. Guess I'll try commenting that top table out of the index page. Just have to figure out which pages besides index.php that's going to affect. gdane
AlanR Posted April 30, 2006 Posted April 30, 2006 Removing Frontpage extensions didn't make any difference for me. Still stuck with 644 on configure.php, which means I'm still stuck with that warning at the top of every page on my store. Not worrying about permissions doesn't make sense. Having that warning sucks. Guess I'll try commenting that top table out of the index page. Just have to figure out which pages besides index.php that's going to affect. gdane You can turn the warning off includes/application_top.php at the bottom // set which precautions should be checked define('WARN_INSTALL_EXISTENCE', 'true'); define('WARN_CONFIG_WRITEABLE', 'true'); define('WARN_SESSION_DIRECTORY_NOT_WRITEABLE', 'true'); define('WARN_SESSION_AUTO_START', 'true'); define('WARN_DOWNLOAD_DIRECTORY_NOT_READABLE', 'true'); Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)
j_may80 Posted April 30, 2006 Posted April 30, 2006 Yep, it's weird. I couldn't get any of the permissions to stick, none. I finally edited the two config files by hand to install. Everything was cool but I couldn't upload any product images through the system. My host removed some hidden fp ext files about that time, and viola, that fixed it.
Guest Posted May 1, 2006 Posted May 1, 2006 Try this: http://www.oscommerce.com/forums/index.php?sho...06entry343806 Thank you! Just wish I knew why it was not working the other ways.
AlanR Posted May 1, 2006 Posted May 1, 2006 Thank you! Just wish I knew why it was not working the other ways. It's the ownership of the files. If you run this little script (just name it whoami.php) it will tell you what user php is running as <?php // outputs the username that owns the running php/httpd process // (on a system with the "whoami" executable in the path) echo 'php is running as user: ' . exec('whoami'); ?> The permissions script works because the file is owned by the same user as php, not you as the ftp user. This may cause you some more problems down the line with other permissions. Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.