install.php Error install.php Error
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

install.php Error

Started by JB2, January 11, 2006, 04:18:25 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

JB2

When I attempted to install via install.php, I received the "You seem to be trying to install the standalone Coppermine into your Nuke portal." error message even though I do not, nor ever had, PHPNuke/PostNuke, etc. installed on my server.  So, I decided to take a look at install.php and discovered the reason.  The check for a "portal" is simply based on the presence of a directory named "modules" two levels above the Coppermine root directory.  I was installing Coppermine directly underneath the Apache2 htdocs directory, so install.php was finding the Apache2 modules directory!  You might want to rethink this check.

Joachim Müller

do you actually use the most recent version cpg1.4.3 - the issue you claim to have existed in cpg1.4.2 and was fixed afaik?

JB2

Yes, I downloaded cpg1.4.3.zip from sourceforge.

Joachim Müller


JB2

I already determined that commenting out the check would fix the problem.  However, the code is still in 1.4.3 and my original comment still stands.  You should consider removing, or at least modifying, the check.  It is rediculous to assume that the presence of a directory named "modules" two levels up from the current directory is evidence of a PHPnuke or PostNuke installation!  A product like Coppermine is a useful tool for non-programmers so the installation shouldn't require editing PHP.  Why not simply warn people that if they attempt to install in an environment with PHPnuke or PostNuke Coppermine will not function correctly?

Joachim Müller

Quote from: JB2 on January 13, 2006, 02:17:00 AM
Why not simply warn people that if they attempt to install in an environment with PHPnuke or PostNuke Coppermine will not function correctly?
Because people don't read docs, especially nuke users don't. We used to have tons of requests from nuke users who complained that the standalone version wasn't working for them, that's why the nuke check was added some versions ago. Complaints from people like you who get caught by the nuke detection routine are very rare, so I'm not sure if we should drop the check, going from bad to worse.