Briging SMF 1.1.5 & CPG 1.4.18 Fatal Error

[tehnoacid]

Hello!
Please help me  :'(

I have the following issue when trying to bridge coppermine 1.4.18 and SMF 1.1.5 :
Coppermine critical error. Unable to connect to database !

This Error only when guests trying go to gallery, but if first login in SMF and then go to the Coppermine - no error

Coppermine install: http://www.kchetverg.ru/fotoforum/
Forum install: http://www.kchetverg.ru/forum/
Coppermine version: cpg1.4.18
Forum version: SMF 1.1.5
Test user account: test
Password: 111222

BridgeManager settings:
Forum URL:  http://www.kchetverg.ru/forum/
Relative path to my SMF config file:  ../forum/
Use post-based groups?:  0 


Please sorry for my english, I'm Russian.

[phill104]

Your English is much better than my Russian.

I get a different error message


"There was an error while processing a database query "

If you disable bridging can you log on successfully in coppermine and smf?

There is a Russian support board if you find that more comfortable though I am not sure how active it is compared to here.

http://forum.coppermine-gallery.net/index.php/board,41.0.html

[Joachim Müller]

"There was an error while processing a database query "

Enable debug_mode to see what query actually fails and post that query (not the debug_output, just the error message).

[tehnoacid]

If you disable bridging can you log on successfully in coppermine and smf?

Yes.

[tehnoacid]

Wow!
After update to CPG 1.4.19 this problem disabled.

[Joachim Müller]

See http://coppermine-gallery.net/demo/cpg14x/docs/index.htm#upgrade_why_reasons
Scroll down a little for the cpg1.4.19 package:

• Danish language file updated
• spacer for empty album list cells fixed
• improper nesting of form-tag in various files fixed
• invalid <f>-tag in upload.php removed
• type translation in reports fixed
• resources consumption for slideshows in meta albums fixed
• hard-coded string "edit keywords" replaced with translation
• Spanish documentation added
• SMF anonymous user fix
• security issue reported at http://www.milw0rm.com/exploits/6178 fixed
• profile email check issue fixed