coppermine-gallery.com/forum

Support => cpg1.3.x Support => Older/other versions => cpg1.3 Installation & Setup => Topic started by: chuckles on January 16, 2005, 08:36:28 PM

Title: install.php wants me to chmod, but I already did
Post by: chuckles on January 16, 2005, 08:36:28 PM
I'm running the latest fedora with apache 2.0 and php 4.3.9. 

I chmod'ed the include and albums directories recursively to 777, but it is saying that I still need to do that and that they aren't writeable.  Any ideas on why this might be happening?
Title: Re: install.php wants me to chmod, but I already did
Post by: Joachim Müller on January 17, 2005, 04:14:02 AM
well, you seem to be the webserver admin, so you should know what permissions are needed to give the php script write access. You could try 755 instead of 777, as suggested in the docs. For details, you should ask your webserver admin - oops, that's you ;)
We have no idea on your webserver config, this issue is not related to coppermine...

Joachim
Title: Re: install.php wants me to chmod, but I already did
Post by: web_guy on February 23, 2005, 05:20:40 PM
what is all that 777, and 755 stuff anyway?
Title: Re: install.php wants me to chmod, but I already did
Post by: Nibbler on February 23, 2005, 05:27:38 PM
http://www.december.com/unix/tutor/permissions.html
Title: Re: install.php wants me to chmod, but I already did
Post by: Joachim Müller on February 23, 2005, 07:03:09 PM
Quote from: web_guy on February 23, 2005, 05:20:40 PM
what is all that 777, and 755 stuff anyway?
how appropriate of you to choose "web_guy" as nickname on this board. You are the web guy then? Ever heard of google?  Try googling for the term "CHMOD" and you should get all the information you need...

Joachim
Title: Re: install.php wants me to chmod, but I already did
Post by: mast76 on March 14, 2005, 12:23:04 AM
Quote from: chuckles on January 16, 2005, 08:36:28 PM
I'm running the latest fedora with apache 2.0 and php 4.3.9.

I chmod'ed the include and albums directories recursively to 777, but it is saying that I still need to do that and that they aren't writeable. Any ideas on why this might be happening?

I have just had the same problem. It turned out to be the SELinux which overruled the write access.

Workaround:
In KDE or Gnome, go to "System Settings" - "Security Level" - "SELinux" and disable it.