xoops bridge failed after 1.4.8 update xoops bridge failed after 1.4.8 update
 

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

xoops bridge failed after 1.4.8 update

Started by chainsawbeer, July 27, 2006, 05:18:25 AM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

chainsawbeer

I have the following issue when trying to bridge coppermine and XOOPs:

Fatal error: main(): Failed opening required '../mainfile.php' (include_path='.:/usr/share/pear') in /var/www/vhosts/chainsawbeer.com/httpdocs/gallery/bridge/xoops.inc.php on line 30

Coppermine install: http://www.chainsawbeer.com/gallery/
Forum install: http://www.chainsawbeer.com/
Coppermine version: cpg1.4.8
Forum version: Xoops v2.2.4
Test user account: cpgtest / cpgtest1

BridgeManager settings:
Forum URL:  http://www.chainsawbeer.com
Relative path to your BBS's config file:  ../
Use post-based groups?:  1

After upgrading to 1.4.8 I received the above error.  I've tried hardcoding the mainfile.php location and changing the bridgemgr switch as well as applying the xoops pathcheck patches.

chainsawbeer

Turned off bridge manager for now till I can track down what's causing the issue... it seems perfectly functional as long as bridging is off.

Joachim Müller

Where is mainfile.php actually located then?

Quote from: chainsawbeer on July 27, 2006, 05:18:25 AM
After upgrading to 1.4.8 I received the above error.
What version did you upgrade from?

Quote from: chainsawbeer on July 29, 2006, 01:58:58 PM
Turned off bridge manager for now till I can track down what's causing the issue... it seems perfectly functional as long as bridging is off.
There's little we could do to actually help you if bridging is off.

chainsawbeer

I've re-enabled bridge manager.  url-wise the gallery is at http://www.chainsawbeer.com/gallery/ while mainfile.php is at http://www.chainsawbeer.com/mainfile.php.  File system locations are /var/www/vhosts/chainsawbeer.com/httpdocs/gallery/ and /var/www/vhosts/chainsawbeer.com/httpdocs/mainfile.php.  I upgraded to 1.4.8 from 1.4.3

Nibbler

Did you try giving the bridge manager the full path to the file?

chainsawbeer

I'm pretty sure I'm doing it correctly... fill me in if not...

I changed
define('USE_BRIDGEMGR', 1);


to

define('USE_BRIDGEMGR', 0);


and


if (!USE_BRIDGEMGR) {
        require_once('../xoops/mainfile.php');
} else {
        require_once($BRIDGE['relative_path_to_config_file'] . 'mainfile.php');
}


to


if (!USE_BRIDGEMGR) {
        require_once('../mainfile.php');
} else {
        require_once($BRIDGE['relative_path_to_config_file'] . 'mainfile.php');
}

Nibbler

Don't edit any file, just use the bridge manager script.

chainsawbeer

Ok.  I reunzipped the 1.4.8 archive and copied the default xoops.inc.php in the bridge/ directory.  I then re-enabled the bridge with the bridge manager and now I'm getting

Fatal error: main(): Failed opening required '../mainfile.php' (include_path='.:/usr/share/pear') in /var/www/vhosts/chainsawbeer.com/httpdocs/gallery/bridge/xoops.inc.php on line 30

again.


the bridge manager settings are

Bridge Wizard: enable/disable BBS integration
Your bridge settings
Forum URL:  http://www.chainsawbeer.com 
Relative path to your BBS's config file:  ../ 
Use post-based groups?:  1 

Nibbler

Quote from: Nibbler on July 29, 2006, 10:58:38 PM
Did you try giving the bridge manager the full path to the file?

ie. /var/www/vhosts/chainsawbeer.com/httpdocs/

chainsawbeer

*slaps self in the forehead*  sorry for the agitation and thanks for the help guys.  Working as a jr admin ya'd think I wouldnt make such trite oversights, but as it turns out, because I'd just migrated the site from a server I had colocated to a virtual dedicated temporarily, I'd forgotten to change ownership back when I un-tar'd the whole shebang and the include directory was still own'd by the old user account.  A quick chown -R and chgrp -R of the gallery directory fixed the entire debacle.  Thanks again and sorry to have wasted your time.