Cpg 1.3.5 conflicting with WordPress 1.5.1.3 Cpg 1.3.5 conflicting with WordPress 1.5.1.3
 

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

Cpg 1.3.5 conflicting with WordPress 1.5.1.3

Started by t.nielsen, December 31, 2005, 03:42:05 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

t.nielsen

I am having the following problem when installing Coppermine and Wordpress on the same server. I cannot really say whether it is an issue with coppermine or wordpress but please bear with me and read on :-)

My goal is to integrate coppermine and wordpress but I never get that far.
I start by installing WordPress - works perfectly
Then I install coppermine using the same db but different prefix for tables and now problems start. After I have run the installation script I get nothing but a blank page.
The same happens when I start by installing coppermine: Works perfectly. But stops working after installation of WordPress

This is quite puzzling to me as both are installed to separate directories and separate tables - thus according to my logic they shouldn't 'be aware' of each others' presence?
This may be the wrong place to ask for suggestions as I am pretty sure that there's something in my setup that causes the problems .. but on the other hand, someone more experienced than me just might be able to point me in the direction of a possible cause

Best regards - and happy new year
Thomas

t.nielsen

... I probably should add that the same thing happens with any combination of WP 1.5.1.3 / WP 2.0 / CPG 1.3.1.5 / CPG 1.4.3

Nibbler

I have just installed WP to test this issue, and encountered no adverse consequences of having done so.

t.nielsen

I appreciate your effort anyway. Thanks. I am aware of lots of people running both wp and cpg without issues .. which suggest that something in my php(?) or other configuration is the culprit

regards
Thomas

Joachim Müller

post a link both to your wp and coppermine installs

t.nielsen

#5
WordPress (currently v.1.5.3.1) : http://www.vespedia.dk/main/index.php
admin-login: http://www.vespedia.dk/main/wp-login.php   
login: removed

Coppermine (v. 3.3) : http://www.vespedia.dk/cpg/index.php

for php-configuration: http://www.vespedia.dk/phpinfo.php

regards

Joachim Müller

http://www.vespedia.dk/ is down for me. Don't post admin logins on public boards, I removed it from above posting. Change the login asap to something less trivial, that's a no-no.

t.nielsen

ahem .. you're right. Wasn't really thinking there. Thanks

both installations are in subdirs .. and nothing resides in webroot

www.vespedia.dk/main/
www.vespedia.dk/cpg/

Joachim Müller

you seem not to understand: nothing happens when going to your page, it is down. This is what I get when pinging it:
QuoteC:\>ping vespedia.dk

Ping vespedia.dk [217.116.240.171] mit 32 Bytes Daten:

Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 217.116.240.171:
    Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 0ms, Maximum =  0ms, Mittelwert =  0ms

C:\>
Although the messages are in German, it should be quite obvious that your site is down, no matter what subfolder you try to access. Are you by chance self-hosted?

t.nielsen

Hm .. that's odd

Sites are acessible to me.

I am not self-hosted and I believe my host may have decided to not reply to pings

Nibbler

It's accessible to me. What are you doing with your include_path ? It needs to include the current directory (.) for Coppermine to work.

t.nielsen

Well right now GauGau seems to be right about the site being down .. I guess you get what you pay for.

Nibbler: include_path certainly looks odd .. and that may very well be the cause.
Can I set include_path in my .htaccess file .. just to experiment without having to wait for support?

kegobeer

Your include path is a PHP variable, not an Apache one.
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

t.nielsen

Problem seems to be solved :-)
And indeed the include_path was the trouble maker. Still I do not fully understand how the presence of WordPress could change this but nevertheless adding the following line to .htaccess helped (Yes, include_path is a php setting but apperantly some of these can be modified through .htaccess)

php_value include_path ".:../:./include:../include"

I realise that my problem was pretty trivial in the end and hope you will excuse me .. :-)
Thank you for your effort in helping me out. It is greatly appreciated :-)

Best regards
Thomas