Which would be a better solution?

[spearfish]

Hey,
I'm looking to develop a community game-like website.  The players would have all sorts of achievements and jazz from the game.  I also would like to have a forum, and it needs to be in sync with the site.

I'm at a crossroad here.  I know that SSI.php will help me work my main site with my forum, but I also know (from experience) that it's buggy.

Which should I do - Modify the forum code to work with my site's user database,  or modify my site coding to work with SMF?

The forum is not an essential part of my site... just something on the side.  But at the same time, the Simple Machines team has already developed scripts that registers, logs in, and logs out users along with some nice data tables.  How easy would it be to mod SMF to recognize a 3rd party user table, and how easy would it be to run off of SMF's cookies?

Opinions would be great,
Thanks

[Kindred]

1- why do you think that SSI is buggy?  I use it for a dozen modules, myself.

2- look in the bridges and integrations board. There are sticky posts discussing how to use third party softwares with SMF. Of course, my feeling is, SMF has good security and a nicely granular permissions system... why re-invent the wheel, when SSI allows access to all of that?

[spearfish]

I decided to go with this, yes.  The security and user tables, cookies, etc. were things I didn't feel like redoing.

And I apologize for calling SSI buggy.  I was having trouble redirecting after a logout, although it was 100% my fault.

Code Select Expand


$site_url = 'http://' . $_SERVER['SERVER_NAME'];
$page_url = $site_url . $_SERVER['REQUEST_URI'];
ssi_logout();
# gahh why isn't this working??


I had finished checking LoginOut.php, placing die() commands at chokepoints to see what was going on, and was halfway through SSI.php when I noticed that....

It made me feel stupid, but I'm glad it works =D