Emails with SQL Error Reports

tjmuse · July 13th, 2010, 06:31 PM

Our upgrade to 7.02 from 6.23 is spitting out a bunch of emailed SQL errors:

Code:

Content visible to verified customers only.

We have avatars turned off in the Gallery. And it appears to be working fine from the user's end of things, there are no errors visible.

Our Gallery is integrated with our SMF Forum (it's RC1 right now, we're only updating one thing at a time...)

Chuck S · July 13th, 2010, 08:20 PM

In your forum/smf2.php integration file change line 293 to this

Code:

Content visible to verified customers only.

tjmuse · July 13th, 2010, 08:32 PM

Thanks, Chuck ... off to try it. I'm kind of remembering we had to fix something in this file for the RC1 install, I'd just opened it in my editor to peer at it when your reply arrived.

TJ

tjmuse · July 13th, 2010, 09:23 PM

It has not fixed the error messages. Of interest, there is *no* field named custom_avatar_url in the smf_settings table.

There is one called avatar_url

But that didn't fix the error messages either. And the error message is still showing that it is trying to pull the smf_settings table out of the photopost database, not the SMF database:

Code:

Content visible to verified customers only.

Until there's a fix on this, I'm totally disabling this line of code. We don't show the avatars anyway.

And I can hardly wait to see the hate-mail from our host about the number of emails this generated.

TJ

Chuck S · July 13th, 2010, 11:33 PM

there is most definately that setting in smf2

Rozay · August 15th, 2010, 09:37 AM

Hey, tjmuse, did you find a workaround for this? I'm having the same issue with photopost classifieds + SMF 1.1.11. How do you disable avatars at all, where is the option? Thanks.

I go reading the smf forums to see if there's something more on this...

tjmuse · August 15th, 2010, 09:55 AM

I disabled it in the php code ... we need to upgrade to the new SMF anyway, and will soon. We don't even use Avatars in the Gallery, so it was doubly annoying.

Since there is no table in our SMF database called what the new Photopost is looking for, it seemed the best thing to do. I don't know whether Photopost is working with an older copy of SMF, or whether ours is the older one and RC3 will fix this error. We've got RC1.2 of SMF 2 installed. Our older PP never had this issue.

Chuck S · August 15th, 2010, 10:29 AM

Yes you need to use the supported code by SMF not an RC