Page 1 of 1

Error message when integrating with Simple Machines

Posted: Wed Jan 17, 2007 9:53 am
by stopsatgreen
I was running CMSMS 0.13 and SMF 1.0 together, using SSI.php to include recent posts from the forum on my homepage.

Recently I upgraded to CMSMS 1.02 and SMF 1.1 and now I get an error message at the end of pages which use the includes:

Code: Select all

Warning: mysql_query(): 8 is not a valid MySQL-Link resource in /home/se5fmorg/public_html/forum/Sources/Subs.php on line 321

Warning: mysql_affected_rows(): 8 is not a valid MySQL-Link resource in /home/se5fmorg/public_html/forum/Sources/Subs.php on line 336

Warning: mysql_query(): 8 is not a valid MySQL-Link resource in /home/se5fmorg/public_html/forum/Sources/Subs.php on line 321
I realise this is more of a SMF problem than a CMSMS one, but I've posted on the forum there and can't get any help. Has anyone here tried something similar and received a similar error message? Has something changed between 0.13 and 1.02 which could have caused this?

I notice that this site uses SMF 1.1 but only CMSMS 0.13, and includes work fine.

Re: Error message when integrating with Simple Machines

Posted: Thu Jan 18, 2007 10:33 pm
by stopsatgreen
Bump

Re: Error message when integrating with Simple Machines

Posted: Sun Jan 28, 2007 11:38 pm
by stopsatgreen
Here are a couple of answers I've had from users on the SMF forum:
It looks like either $db_connection isn't being defined somewhere, or it's being redefined.
http://www.simplemachines.org/community/http://phpbb.cmsmadesimple.org//viewtopic.php?p=915685#p915685
If you calling SMF functions and use SSI you shoud use the db_query function
http://www.simplemachines.org/community/http://phpbb.cmsmadesimple.org//viewtopic.php?p=898539#p898539

Is anyone able to point me in the right direction?

Re: Error message when integrating with Simple Machines

Posted: Mon Jan 29, 2007 4:55 pm
by Jo Morg
I'm not sure, but it actually seems that this particular error is related to the SMARTY engine. I've been trying to get this error solved for months without results. Since it only appears once per session (in my case...) I just concealed it with div tags to wrap my contents after setting the BODY to have the same color and background color. Not nice, but at least I'm the only one who knows its there. ::)
However if anybody else has a real solution for this issue, I'd be happy to know it too.