SMF Integration

tjmuse · March 1st, 2009, 10:21 PM

New Photopost customer ... hence, brand new install. Using GD option on Apache server. all specs met or exceeded on requirements.

Using the new SMF 2 RC1, and attempting to integrate it into PhotoPost. Both the SMF 2 and PhotoPost are new.

All went fine until I got to step 5 in the install process, at which time it spits out an error:

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/...path.../...to.../Gallery/forums/smf.php on line 567

I note there is smf2.php and smf.php, but this was for smf.php

So, all the settings were fine up until this point, and I'm pretty sure it had accessed the Forum User table in that db before now.

We're looking for ideas how to finish this little issue and get our PhotoPost going.

Thank you for any ideas here.

Chuck S · March 2nd, 2009, 06:32 AM

Well I would suggest you check your installing correctly there should be a SMF and SMF 2

Looks like you selected the main smf 1 not smf 2

reinstall and pay attention to all the options because also on smf you need to explicitly enter the cookie name and smf table prefix for things to work.

tjmuse · March 2nd, 2009, 10:06 AM

I will go back and do it again, but I'm pretty sure that SMF2 was what I selected in the pull down menu in one of the previous steps.

back with the results in a bit.

Chuck S · March 2nd, 2009, 10:20 AM

Code:

Content visible to verified customers only.

Edit the install script your correct little bug it should say smf2 not smf on the value for the option.

tjmuse · March 2nd, 2009, 10:41 AM

Chuck: I have attached the screen shot just before I pressed the submit button to go on.

It is clearly set for SMF2 - and the error message at the top of the Step 5 page still says:

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /path/to/Gallery/forums/smf.php on line 567

I looked up the cookie name myself, and although I didn't install the Forum, the person who did install it didn't alter any of it's defaults. So I'm fairly confident the prefix setting needs nothing else there.

The thing that set off the alert in my head and why I came here before digging any deeper in this config, is that the file where the error was specified says smf.php and not smf2.php.

If you can confirm that it is supposed to be using the smf.php file and not the smf2.php file, I will do some more work in figuring out what was done during the Forum install.

Thanks!

Chuck S · March 2nd, 2009, 10:41 AM

Please read my last post.

Your second error is because you have not entered the correct table prefix for your smf database tables.

tjmuse · March 2nd, 2009, 10:48 AM

Whups, we cross posted, I see your message and will make the correction to the install file, thank you Chuck.

Chuck S · March 2nd, 2009, 11:00 AM

No problem let me know if you need anything else and take note of your forum table prefix so you dont run into that second error.

tjmuse · March 2nd, 2009, 11:11 AM

Thanks again, that went through without errors, and the Admin login for the Forum works, so I'm thinking we're gold!

Chuck S · March 2nd, 2009, 11:13 AM

Yep no problem have a good day.

tjmuse · March 2nd, 2009, 07:08 PM

Last question for the day, more of a heads up, I think.

Do people normally set GD2 up during install and still have to select it in the Admin settings/Global options to get it to actually use GD2?

At first it spit out a mogrify error. I scratched my head, thinking, what?! I didn't tell it that.

After visiting the Global Options and turning on GD2, uploads were perfect.

Chuck S · March 2nd, 2009, 08:22 PM

Not that I am aware of but I will check the install thanks.