So then it must be a bug, because that is was is set in "isStart". The role "Registered" is what i set manually to make it work, but that is also what is set in "isStart".

So basically the users aren't being added to a group for some reason when they are logged in and first visit the forum.

Yep - getting the same problems here. We could really do with Jaben having a look at what's going on with this!

I shall explain the issue again, just in case he has a look in here:

FYI - I'm running YAF Version 1.9.3 beta, alongside an existing .NET 3.5 application.

Syncing with my existing aspnet Membership provider is working great. The Roles have been ported over and [Linked] into YAF, and have been set up with the correct Access Masks and with [IsStart] set to true.

When I log in as an existing membership prov. user, the user details are ported over to YAF and everything seems fine.

The only problem is that the new user (and associated GroupID) is not added to dbo.Yaf_UserGroup table.

Thus, when you log in as the user you have less access rights than a Guest!

Has anyone found a workaround for this, or located the reason for this happening? I presume that Jaben had this working in his integration, otherwise it seems to me that the whole concept of syncing with an existing membership provider would be worthless. You cannot add users to groups manually on an ad hoc basis!

It just seems so strange, as you would have thought that the 'User porting/creation' function would have the porting role/group functionality rolled up with it?

It's frustrating, as I feel I'm about 1 step away from having YAF seamlessly integrated with my application and have just fallen at the last hurdle

Help me Obiwan Kenobi, you're my only hope

I had the same issue with my integration...but it's not really a bug in the YAF code...just really a disconnect in the processes/workflows...


What I noticed that was happening...

With the ASPNETDB manager/role provider (yeah i know the db is separate from the "provider"...but whatever) when users are created, the default is for them not to be automatically assigned "roles"(unless you modified/added code to do it).

So when YAF goes and grabs a user created through that default process, its grabbing a user with a null value for a "role."

Now I ain't the brightest bulb on the strand...but...

If you cant imagine the problems referencing "null values" creates, you shouldn't be touching code, you won't ever come near one of my computers, if you work in IT you should hand back all your wages you've earned so fraudulently, and go jump in front of a #@$%@ truck (lorry (sp?)for you peeps across the pond)...cuz you are worthless....

So easy solution that people hinted at earlier...have your "parent" app define a "role" for new users upon their creation...worked for me

Well the simplest way to solve this is make sure that your application roles match exactly your YAF roles. Then there isn't an issue. If it's a brand new app, not a problem.

If it's an existing app, then you need to decide which roles to use, the new YAF or your old roles. Either way, you need to make the modifications so proper roles are assigned.

I've deployed v1.9.3 first time, I've gone with using YAF roles, in addition to using the YAF signup and account management. Saves me from creating my own account management crap!