Installation error? Problem with coppermine folder Installation error? Problem with coppermine folder
 

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

Installation error? Problem with coppermine folder

Started by dafyd, July 01, 2004, 09:13:04 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

dafyd

My install of Coppermine at http://www.ministry-of-magic.net/gallery appears to have been successful.

However, Coppermine keeps trying to redirect me to the minstry-of-magic.net root folder, instead of the Coppermine one.

For example, when I try to update http://www.ministry-of-magic.net/gallery/config.php, it tries to send me to http://www.ministry-of-magic.net/config.php (which doesn't exist).

I have installed Coppermine on other domains in the same way (I think) and it works fine... so what am I doing wrong here?!

Casper

It has been a long time now since I did my little bit here, and have done no coding or any other such stuff since. I'm back to being a noob here

dafyd

I've tried renaming config.php as suggested, but it still doesn't work.

The problem is not just centred on the config menu - when accessing albums it often looks for them in the site root instead of the gallery root... one level up.

Is there a configuration setting that I've changed (or not changed) that is making it do this?

Casper

Make sure your config setting 'target address for....', shows the full url, i.e., http://www.yoursite.come/your_coppermine_directory/
It has been a long time now since I did my little bit here, and have done no coding or any other such stuff since. I'm back to being a noob here

dafyd

That was the first thing I checked... still no difference.

I've uninstalled the gallery and installed Coppermine 1.3 (I was using 1.2.1 before)... but the problem remains!

I don't understand why it is happening!