talon Posted February 23, 2004 Posted February 23, 2004 Every time I install this I always end up struggling with this error. If I remeber correctly it's an ownership problem. I have read the forum and tried everything. Chmoded to 644, 444... you name it. Downloaded the configure.php file then deleted it from the server and re-uploaded it. Didn't work. I struggle with this error every time I install this script on every server I have ever installed it on. I would have hoped by now the solution would be a sticky topic in the forum. I am on a Linux redhat 8 server running Apache and PHP 4.3.2. My installs are always on linux server so this may be a factor. It seems that the problem has something to do with the fact that the file is created by the server during the install. This causes an ownership problem. Getting the permissions correct for this file can be a real headache for someone who does not have root access. If their is a simple way to get the permission correct on this file other than what I have already tried, please post it. If the only solution is to chown the file, please provide detailed instructions. I would also request that this info be made a sticky topic or somehow easier to find. I searched the forums and found tons of threads by Windows users and folks suggesting the obvious. I am shocked more people do not run into this problem. Also the installation instructions suggest you rename the admin folder before you run the install script. This is a bad idea and results in error. Better to wait until after the install to rename the admin folder.
talon Posted February 23, 2004 Author Posted February 23, 2004 I found one solution that works in this particular situation. Though I doubt that this will work for everyone who runs into this. Chmoding via FTP clients does not work, because the file instantly reverts to its former permissions. It seems to successfully chmod, but in reality the permissions do not change. The only way I was able to get rid of the error was to login into my account on the server via SSH and chmod it from the command line to 555. Why this works and the FTP clients do not is a mystery to me. If anyone has an alternative method to solve this issue, please post it for others having this problem.
seatonyhill Posted February 26, 2004 Posted February 26, 2004 Hi. I followed you until you changed it through SSH - what's SSH? I've spent so much time via FTP trying to fix this! I'd rather be doing the other fun stuff. Thanks.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.