I have the following issue when trying to bridge coppermine and SMF

[scooby1350]

I have the following issue when trying to bridge coppermine and SMF:
Critical error: There was an error while processing a database query

Coppermine install: http://test.gdiracing.com/coppermine
Forum install: http://test.gdiracing.com/simplemachines/
Coppermine version: cpg1.4.3
Forum version: SMF 1.0.6
Test user account: test / test1234

BridgeManager settings:
Forum URL:  http://test.gdiracing.com/simplemachines
Relative path to your BBS's config file:  ../simplemachines/
Use post-based groups?:  0 

These both are fresh installs. Every time I click enable that is the error message I get. Any help would be great.

[Nibbler]

Enable debug mode first and post the mysql error message that you get (not the entire debug output).

[scooby1350]

While executing query "SELECT group_id, group_name FROM cpg143_usergroups WHERE 1" on 0

mySQL error: Table 'testbb.cpg143_usergroups' doesn't exist

Hope this is it.

[Nibbler]

There's a workaround already posted for that, check previous threads on the subject.

[scooby1350]

Sorry I tried to find the thread with the work around, but all I could find is the bridge problems with phpbb and not with SMF. Could you post the link Please. Thanks.

[Nibbler]

http://forum.coppermine-gallery.net/index.php?topic=24842.0
http://forum.coppermine-gallery.net/index.php?topic=27126.0

[scooby1350]

Ok great it is working great, but is there a way that when you login through coppermine to have it take you back to coppermine instead of the message board. I install the bridge with phpbb and after login it takes you back to the photo page or is this a setting in the message board software?

[Nibbler]

Did you try disabling database sessions in SMF ?

[scooby1350]

That fixed that now I get this when ever I try to update anything in the groups: Fatal error: session_start(): Failed to initialize storage module. in /home/adubey/public_html/test/simplemachines/Sources/Load.php on line 1135

[Nibbler]

Then you'll need to either fix that (ie. google for your error message) or revert to db sessions and work around the redirection issue.