Getting errors on setup

[dukhunter99]

I am installing cop 1.3.2 on server so I can bridge with smf. my hosting company (midphase) uses fanastico for installation which installs it in its own database. I have a database set up for both cpg and smf. I decided to install coppermine manually but now I'm getting errors. The errors state:
Before you continue with Coppermine installation, there are some problems that need to be fixed.


--------------------------------------------------------------------------------

The 'include' directory (located in the directory where you uploaded Coppermine) should be writable in order to save your configuration. Use your FTP program to change its mode to 777.


--------------------------------------------------------------------------------

The 'albums' directory (located in the directory where you uploaded Coppermine) should be writable in order to allow pictures upload. Use your FTP program to change its mode to 777.


--------------------------------------------------------------------------------

The 'userpics' directory (located in the 'albums' directory on your server) should be writable in order to allow pictures upload. Use your FTP program to change its mode to 777.


--------------------------------------------------------------------------------

The 'edit' directory (located in the 'albums' directory on your server) should be writable in order to allow pictures upload. Use your FTP program to change its mode to 777.

Once you are done, hit the "Try again" button.

Can someone tell me what to do!

[kegobeer]

First, read the documentation.  It explains how to install Coppermine.  You have to change permissions on some files/directories.

[OmegaGOD]

The answer to your question is IN your question itself :-)

--------------------------------------------------------------------------------

The 'include' directory (located in the directory where you uploaded Coppermine) should be writable in order to save your configuration. Use your FTP program to change its mode to 777.

--------------------------------------------------------------------------------

The 'albums' directory (located in the directory where you uploaded Coppermine) should be writable in order to allow pictures upload. Use your FTP program to change its mode to 777.

--------------------------------------------------------------------------------

The 'userpics' directory (located in the 'albums' directory on your server) should be writable in order to allow pictures upload. Use your FTP program to change its mode to 777.

--------------------------------------------------------------------------------

The 'edit' directory (located in the 'albums' directory on your server) should be writable in order to allow pictures upload. Use your FTP program to change its mode to 777.

Once you are done, hit the "Try again" button.

[richardc020]

I've an identical error yet I've already chmod-ed 777 with proof:

Code Select Expand


drwxrwxrwx 2048 Jun 13 21:25 include/
drwxrwxrwx 2048 Jun 13 21:25 albums/
drwxrwxrwx 2048 Jun 13 21:25 albums/edit/
drwxrwxrwx 2048 Jun 13 21:25 albums/userpics/

Likewise when all are set to 755 or 0777 (I don't know if that's the same as 777). /path/install.php's test_fs's is_writable() all result in false despite the directories being 777-ed.

Aside, I've read /path/docs/faq.php and /path/docs/manual.php and my host has no open_basedir restriction and php safe mode is off.

What is the solution to getting /path/install.php to work?

[Joachim Müller]

ownership?

[thomas461]

I am having the exact same issue. I am on day two trying to figure it out. At first there was a problem with 403 errors and some SElinux permissions errors.  But now it comes up with the change permissions screen.  All of the "required/listed" directories have been changed to 777.

I downloaded 1.3.3 this morning hoping it was just something in 1.3.2.  Unfortunately, same problem. 

Oh I have also changed the directory owner  from root to apache to nobody and nothing seems to work.

[Nibbler]

Some people have reported that disabling selinux solves the problem for them.

[richardc020]

It may be ownership but:

Code Select Expand


>: ls -l public_html/photos/albums
total 12
drwxrwxrwx   2 rc46     30          2048 Jun 13 12:31 edit/
-rw-r--r--   1 rc46     30          1401 Jun 13 12:31 index.html
drwxrwxrwx   2 rc46     30          2048 Jun 13 12:31 userpics/
>: whoami
rc46
>: chown nobody public_html/photos/albums
chown: public_html/photos/albums: Not owner
schiff-56 rc46>: chown nobody public_html/photos/albums/edit
chown: public_html/photos/albums/edit: Not owner

Translation: it refuses to allow even me myself to edit.

I give up. This is stupid.