forum.coppermine-gallery.net
Support => cpg1.4.x Support => Older/other versions => cpg1.4 bridging => Topic started by: greyias on December 09, 2005, 03:22:08 am
-
I just recently changed my forum from phpbb to SMF, and so I was trying to change my bridge files, but due to unforseen circumstances, I cannot boot up the computer in which I have the instructions for 1.33 bridging, so I was running a little blind. I decided to upgrade, hoping I could re-bridge the files later.
On it's own, it works fine, but when I go into the bridging wizard (and everything is set up right as far as I can tell), and enable bridging with SMF I get a fatal error. In debugging mode, it gives me a bunch of stuff that boils down to this MySQL error: mySQL error: Table 'lupous_xmb3.cpg133_usergroups' doesn't exist.
I'm a little confused. Is it trying to find the old usergroups (that were previously phpbb), and can't now?
-
First of all, make sure you have the latest versions of the bridging files from cvs, they fix all known bugs.
udb_base.inc.php (http://cvs.sourceforge.net/viewcvs.py/*checkout*/coppermine/stable/bridge/udb_base.inc.php)
smf10.inc.php (http://cvs.sourceforge.net/viewcvs.py/*checkout*/coppermine/stable/bridge/smf10.inc.php)
bridgemgr.php (http://cvs.sourceforge.net/viewcvs.py/*checkout*/coppermine/stable/bridgemgr.php)
If you still have the problem, let me know.
-
Thanks. That fixed the original problem, but now I get this message (and it displays the offending file):
Fatal error: Call to a member function on a non-object in /home/lupous/public_html/piccy/include/init.inc.php on line 265
I downloaded this version from the Arizona mirror on sourceforge, if that helps any.
-
(and it displays the offending file)
What do you mean ?
-
I thought it was displaying the file that caused the error, but I just checked again (and took it out of debug mode to be sure) and it's actually displaying the smf bridge php file (like the actual php text of author, version, code, etc). Is that normal?
-
No, that's not supposed to happen. Make sure you uploaded the file properly and use a simple text editor.
-
Downloaded and re-uploaded the file, but it's now giving me the original error:
priv_upl_need_approval FROM cpg133_usergroups WHERE group_id in (1,14)" on 0
mySQL error: Table 'lupous_xmb3.cpg133_usergroups' doesn't exist
-
It's looking for the Coppermine usergroups table. Is it looking in the wrong database for it ?
-
Yeah, it's looking in the message board for it, not the gallery. Would copying the table into xmb3 fix this? (I'm wondering if this is something left over from the original bridge to the phpbb board in cpg1.33, as I didn't know how to disable the bridging there).
-
OK, I found the problem. SMF hijacks coppermine's database connection. Edit smf10.inc.php, find
// Connect to db - or supply a connection id to be used instead of making own connection.
$this->connect($db_connection);
Change it to this
// Fix our db connection
mysql_select_db($CONFIG['dbname'], $CONFIG['LINK_ID']);
// Connect to db - or supply a connection id to be used instead of making own connection.
$this->connect($db_connection);
-
Awesome! That looks like it fixed the problem! Thanks so much!
-
I seem to be having what looks, on the surface like the same problem:
I had a working install of 1.44 and have installed 1.48, changing the config.inc.php settings to point to the old database. I've copied across the albums folder with all the images. I can see thumbnails in categories just fine, but when I go to view an intermediate picture I get:
mySQL error: Table 'user_smf.cpg148_comments' doesn't exist
Notice that once again, it's using my SMF db and requesting a cpg table. I've disabled database sessions, cleared my cookies, applied the code hack to smf10.inc.php, rubbed together my rosary beads, run update.php, re-run the bridge manager, made sure that page compression is off, read dozens of posts and I'm still getting the same error.
I'm on:
CPG 1.48
J! 1.0.10
SMF 1.1 RC2
Oristo's Bridge 1.15
Stramms Modpack for 1.48
Any ideas appreciated!
-
You have a different setup. Trying to hijack an old thread that is marked as "solved" is not a bright idea. Start your own thread, doing as suggested in the sticky thread on this sub-board. Locking.