The installer can not find the '/usr/bin/' directory... The installer can not find the '/usr/bin/' directory...
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

The installer can not find the '/usr/bin/' directory...

Started by Rijn, October 07, 2004, 05:26:02 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Rijn

I specified the path; /usr/bin (tried /usr/bin/ as well); i checked with my host provider and he told me that ImageMagick is installed on that path but i cant get past that install screen...

The installer can not find the '/usr/bin/' directory you have specified for ImageMagick or it does not have permission to access it. Check that your typing is correct and that you have access to the specified directory.

...is all i get.  The server admin at the hosting company said the following when i explained it all to his simple Australian arse:
"Could you specify to use NetPBM instead and keep the path at /usr/bin.  The netpbm binaries are there without without question.  The ImageMagick binaries are also there (X11, mogify etc).  /usr/bin is definitely accessible......"

Anyone have any insight to lend here?

Thanks :)

Joachim Müller

Install Coppermine anyway, leaving the ImageMagick path blank in Coppermine installer (telling Coppermine to use GD instead). When the initial setup is done druing install (meaning: your database entries have been built), go to Coppermine config and switch from GD to ImageMagick there. Specify the path in coppermine config, and enable debug_mode (at the very bottom of the screen). Then try to upload a pic - should give you detailed error messages then. If you still get an error message, search the board for it and/or post it here. There are known issues for some users who were not able to set the Use of ImageMagick directly durning install, but they were able to use the workaround described above, not sure why.

Joachim

Rijn

Tite! you solved it!  Thanks a million, this thing has been driving me nuts for days.  ::)