SMF Module

Quote from: Carsten at Dec 16, 2005, 11:50 AM

If SMF is going to be a hassle to work around due to the licensing then why continue with it?

There is the minor point that we’ve got almost 3000 users and 13000 posts...

I thought somebody here said that mercuryboard was GPL and possibly just as good or maybe not even better. (maybe I got the board wrong but still same idea).

I don’t think it would handle the types of things we need to run the forums as well. I could be totally wrong of course. I’ve got Brook’s code he had done on Mercury if anyone’s interested (he removed himself from the online world!).

My thouhgt on this and at the moment is that maybe it would be better to team up with the original coders of a forum and work together to provide a killer solution

That’s a great idea. Are you volunteering to head up the effort. I don’t remotely have the bandwidth for something like that at the moment.

Quote from: chanh at Dec 16, 2005, 11:10 PM

I talk with the developer from http://newsboard.unclassified.de/ and he is very freindly and is planning on a feature to let other CMS to integrate with his board.  I am sure if you approach him something good could happen.

The latest version is 100% XHTML compliant and look beautiful! and no table!

Very cool! I really wanted to use Unclassified when we started this, but it wouldn’t run under PHP5 at the time, so I had to find another solution. Anyone know anything about the possibility of porting our users/posts into their board (from SMF)?

Not available for SMF

http://newsboard.unclassified.de/download#import

regards,

zi

*IMPORTANT*

Please read this recent thread,

http://newsboard.unclassified.de/forum/thread/481

Some serious processing speed discussions.

hope it helps to get an overview, if UNB is good for us or not.

regards,

zi

Quote from: OpenGeek at Dec 16, 2005, 09:25 PM

@Raymond, is there absolutely no way to make the SMF module work?  I thought you had it working at some point?  Is there no API call in the API they provide to pass the credentials and determine if they are valid for the SMF user?

Sure it’s working but the problem exist with imported SMF users.

I think I can get it to work with Susan’s cool idea about using a general password but I don’t have to time to focus on SMF at the moment.

http://newsboard.unclassified.de/

I don’t think I like the looks of this forum at all.

Quote from: xwisdom at Dec 17, 2005, 09:17 PM

Quote from: OpenGeek at Dec 16, 2005, 09:25 PM

@Raymond, is there absolutely no way to make the SMF module work? I thought you had it working at some point? Is there no API call in the API they provide to pass the credentials and determine if they are valid for the SMF user?

Sure it’s working but the problem exist with imported SMF users.

I think I can get it to work with Susan’s cool idea about using a general password but I don’t have to time to focus on SMF at the moment.

If the specific problem is that you can’t sync the passwords, then the solution is allow the SMF authentication routine handle authentication 100% and ignore local authentication -- the imported user can still be used to represent the user in MODx, but credentials are maintained in SMF. Is this the issue?

The problem here Jason is that we don’t know the user’s password during export or import.

If we export MODx users to SMF we can’t authenticate the user or recreate the password in SMF’s format.

If we import SMF users into MODx we can’t authenticate the user or recreate the password in MODx’s format.

If you say bypass local authentification then we will not be able to handle 100% MODx users. Remember that MODx can have more than one connectors/modules that needs to authenticate against other systems

To have a two way bridge yes, but we can at least offer a way to do a one way bridge, where we can import users (ignoring their passwords) from SMF and reference them in both systems, just always using SMF to authenticate those users, regardless if they are logging in from a MODx login form or inside SMF. This is the purpose of the pluggable, chainable authentication structure I have already proposed, based on a tried and tested implementation, but using our very own plugins to do the configurable work. From the manager we would simply need a way to specify the plugins (our local authentication would become a default plugin) for authentication, and give them an order and rules (i.e. fail the entire chain, continue, etc.), we could make it work just about anyway we wanted to.

Quote from: OpenGeek at Dec 17, 2005, 09:59 PM

From the manager we would simply need a way to specify the plugins (our local authentication would become a default plugin) for authentication, and give them an order and rules (i.e. fail the entire chain, continue, etc.), we could make it work just about anyway we wanted to.

Hmmm, can’t we do that with the OnWebAuthentication event? To bypass the modx authentication system you just always set the output to true.