Print

[treehstn]

Hi everyone,

I moved my site to a new server and e107 is working fine.  The integration bridge between e107 and coppermine was not working when I tested it.  Coppermine was there and accessible.  I logged in with the admin account with no issue.  When I tried to run the bridge manager it got most of the way through the process and at the end of it I received this error message:

E107 BRIDGE ERROR: can't find 'e107_config.php'

Then I couldn't get back to the login page or any other page in coppermine without getting the same message.  I found the following post:

http://forum.coppermine-gallery.net/index.php/topic,38615.msg182439.html#msg182439

I did this "check the xxx_config table and look for value of bridge_enable it should be 0" and was able to get back to the gallery.  I tried running the bridge manager again and got the same result. 

The site address is:

www.glassresearch.net/coppermine

I created a test user who's login/pwd is test/test.

[phill104]

Have you checked that the e107 file referred to is actually there and that bridge manager is pointing to the right place?

It also looks like you are running an outdated version of coppermine. You need to upgrade to the latest release before doing anything else.

[treehstn]

Looks like I missed 1.4.17.  I'll upgrade that.  I do know that the e107 file is there.  I'll check to make sure that the bridge is looking in the correct place after I run the upgrade.  If that doesn't fix it I'll reply here again.

Thanks!

[treehstn]

Now that I'm looking at this I didn't miss the upgrade.  I had the installation correct on the old server.  My new webhost performed a cPanel transfer of the whole domain from the old server to the new.  Something must have happened in that transition.  I'm upgrading the install.

[treehstn]

I've upgraded coppermine and it's running fine.  I also reloaded the e107 bridge file.  I checked the file paths in the config area while I was logged in as administrator.  Everything looks ok.  When I run the bridge manager I get the same error message.  One thing that I've noticed is that the actual bridge file names are in this format:

e107.inc.php
mambo.inc.php

But the error message looks like it's looking for a file named e107_inc.php.  I don't want to change the file name itself since it appears to be correct.  It looks like there might be a setting somewhere in the bridge or config files that is using the underscore instead of a dot?

[Nibbler]

The e107_config.php file is part of e107. It is the path to this file that you need to provide to the bridge manager.

[treehstn]

Thanks Nibbler!  I went back through the bridge manager and found the toggle to see unused fields.  It appears that the e107 bridge is setting those paths without any help.  In fact, during the bridge wizard process it won't make the path fields accessible for me to input them.  At that point I figured the paths have been set in the database from a previous bridging on the old server or it may be in one of the .php files.  I've searched through the obvious (and not so obvious!) db tables and .php files and haven't found anywhere that the paths are set. 

Thank you for taking the time to help me with this!

[treehstn]

I've still not been able to find a solution yet.  I'm hoping that thanking Nibbler didn't make my last post look like the problem was solved.

[Nibbler]

The bridge file modifies include/config.inc.php - check that information there is correct.

[treehstn]

The info in include/config.inc.php is all correct.  It doesn't have any path information though in that file.

[treehstn]

I figured part of this out.  I was able to change the following values in the database manually.  Then the bridge started working to a point.  I'm beginning to think this might be a permissions issue.  I'm working on researching that.

1. full_forum_url
2. relative_path_of_forum_from_webroot
3. relative_path_to_config_file

I'm not sure what to set the cookie prefix to. 

It's not wrapping at the moment... I'm working on that also.

[treehstn]

I got the gallery wrapped with e107.  Was just a matter of selecting the e107 theme in CM.  Looks like all is working now.

Thank you for the hints!  They sent me in the correct direction for the fixes.