Problem with paths Problem with paths
 

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

Problem with paths

Started by FrankD, October 14, 2004, 09:10:44 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

FrankD

Hi,
I have a perfect working version of the 1.2 Coppermine.
When I upgrade to 1.3.2 the problem is after the upgrade the paths are not correct.
I tried to upgrade the paths in the index.inc.php but that doesn't solve it completly.

Is there another file I need to add the paths ?

Greetings,
Frank

kegobeer

Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

FrankD

If you see the paths in the source, it's spelled as ../include
While it should be /web/www.doorhof.nl/models/include

So I changed that in one source file but I believe there are more sources ???

Greetings,
Frank

Joachim Müller

Quote from: FrankD on October 14, 2004, 09:10:44 AMI tried to upgrade the paths in the index.inc.php but that doesn't solve it completly.
There's no file "index.inc.php" in coppermine. What version are you using?

Joachim

FrankD

I'm very sorry it was the init.inc

You can find the album on www.doorhof.nl/models

Greetings,
Frank

Joachim Müller

you're using cpg1.3.0
Upgrade to the latest stable release cpg1.3.2

Joachim

FrankD

That's the problem :D.
When I do that I get the path errors.

FrankD

Warning: main(include/config.inc.php): failed to open stream: No such file or directory in /home/.sites/143/site2/web/privat/include/init.inc.php on line 201

Fatal error: main(): Failed opening required 'include/config.inc.php' (include_path='/usr/sausalito/ui/libPhp:/usr/sausalito/ui/web') in /home/.sites/143/site2/web/privat/include/init.inc.php on line 201

FrankD

Warning: main(include/functions.inc.php): failed to open stream: No such file or directory in /home/.sites/143/site2/web/privat/include/init.inc.php on line 223

Fatal error: main(): Failed opening required 'include/functions.inc.php' (include_path='/usr/sausalito/ui/libPhp:/usr/sausalito/ui/web') in /home/.sites/143/site2/web/privat/include/init.inc.php on line 223

This happens after changing the paths in the init.inc
And here I'm stuck :(.

Greetings,
Frank

Joachim Müller

Quote from: FrankD on October 18, 2004, 10:36:00 AMThis happens after changing the paths in the init.inc
I don't understand: why are you changing paths, you're not supposed to?

Joachim

FrankD

Very simple when I don't I get the first error.

I have 3 albums running.
One has been upgraded and works perfect after editing the paths in the init.inc
The other two won't run any other way even after that upgrading.

Do you know if it possible to make a whole new install and than copy all the pictures over, they both have an enormous ammount of pictures.
Otherwise I have to be stuck on 1.3.0

I have to say that the install is in a subdirectory so www.doorhof.nl/models and not in the root www.doorhof.nl maybe that's the problem ???

Greetings,
Frank

Nibbler

Playing with paths isn't the answer - fixing your include_path setting is. It is not allowing includes from the same directory.

FrankD

please rewind that one and explain so I can understand :D.

I can fiddle a bit in the meantime but I really need a bit more explanation my friend, thanks for helping me solve this by the way.

There must indeed be a path problem because for example my ratings also doesn't show, it shows in the small area's the correct gifs/path but when I ask top rated it gives a whole lot longer path.

Please help ???

Greetings,
Frank

kegobeer

include_path is a php.ini setting.  That's what needs to be fixed.
Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

FrankD

I will post this to my provider.

Thanks,
Greetings,
Frank

FrankD

Problem solved by provider :D.
Not php.ini but something with rights.