Permissions set at 777 - install.php says they are not

[jwray]

The Coppermine installation script reports that permissions on include/albums/userpics/edit are not writeable, yet all 4 folders -are- set at 777, and seen that way from both FTP and from a shell prompt.  There are no errors reported in the error log, all v1.4.19 files were re-uploaded twice with no problems, ownership of all files are consistent with the user account, nothing appears unique or out of place.

Linux
PHP v4.2.3 under Apache 2.0.40
MySQL v3.23.58

Install URL:

   http://www.bluecollarsailor.com/cp/install.php

Any ideas?

[Joachim Müller]

On your webserver, something else than 777 might be needed. Did you read the permissions section of the docs?

[jwray]

On your webserver, something else than 777 might be needed. Did you read the permissions section of the docs?

Yes, I read the permissions section of the docs - twice.  Have tried setting ownerships differently, and tried about every combination of permissions possible -- incluing making everything inand below the Coppermine folder 777, letting apache own all, etc;  changes that have never been required on any site on this server.  Oddly - WordPress installs & runs without issue #1 - but all versions of Coppermine I try stop at the same install point.  There is fundamentally nothing unique about this server, nor about the site itself.  All-in-all its basically a generic hi-horsepower LAMP server.  Am really floored on this one.  We have used multiple Coppermine installs in the past for 10,000+ image galleries without ANY install issues at all.  This one is 'more than frustrating'.  Just makes no sense.  Even tried v1.4.19, v1.4.6, and v1.3.2 - all die at the install permissions check.

What "something else then 777 might be needed" might you reccommend?  Defeat is a horrible thing to accept (smile).

[phill104]

Try 755 as outlined here

http://coppermine-gallery.net/demo/cpg14x/docs/index.htm#permissions

Last time I set up a server I accidentally set the root users folder to admin instead of root ownership and that caused the same problem.

[jwray]

Try 755 as outlined here

http://coppermine-gallery.net/demo/cpg14x/docs/index.htm#permissions

Last time I set up a server I accidentally set the root users folder to admin instead of root ownership and that caused the same problem.

Thanks, but I tried that too...  Its enough to cause premature senility.

[jwray]

Please consider this request closed.  The site was moved to another server and Coppermine functioned fine.  Whatever created the problem must have been caused by server configuration and was not a Coppermine problem.

Apologies and thanks.

[Joachim Müller]

Thanks for returning and resolving your issues. Usually, if nothing helps, there is a CHOWN issue, which is something only your webhost can resolve. That's why this sentence exists as a summary of the permissions section of the docs:

If you can't figure how to set permissions properly, ask your webhost for support.