Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Programmatically adding rolesProgrammatically adding roles
Previous
 
Next
New Post
3/19/2007 6:23 AM
 
Hi All,
I'm having trouble programmatically adding new roles. AddRole always returns -1 and no exceptions are thrown. I've had a look around and can't find much information on doing this. Is there anything I'm missing from my code below?

private int AddRole(string RoleName)
{
        PortalSettings ps = dnn.Entities.Portals.PortalController.GetCurrentPortalSettings();
        DotNetNuke.Security.Roles.RoleController rc = new RoleController();              
        RoleInfo ri = new RoleInfo();      
        ri.RoleName = "Testing";       
        ri.PortalID = ps.PortalId;
        return rc.AddRole(ri); // result is -1
}

What I want to be able to do is create a new role and then add a user to that role. It doesn't have to be on the fly (I understand there are some cache issues there?) as the user will not be logged on at the time.

Using DotNetNuke 4.4.1.

Thank you,
Stuntbeaver

 
New Post
3/19/2007 8:37 AM
 

I've used similar code before without a problem. I took a look at both the RoleController.AddRole method and the AddRole stored proceedure and believe that the most likely reasons that AddRole would fail are 1) Invalid PortalId and 2) RoleName already exists.  Have you checked both of these possibilities?  Also, there is a foreign key restraint set up on the RoleGroupID but this should be satisfied if RoleGroupID=0 which it will be by default.

EDITED: On second thought, it looks like the RoleGroupID does have to be set to -1 for the default Global Roles group so that it will be passed as a null to the stored proceedure. After instantiating a new RoleInfo object, try setting RoleGroupID to -1 before calling AddRole.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
3/19/2007 9:09 AM
 
Hi imagemaker - setting RoleGroupId to -1 worked like a charm. Thanks for your help!
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Programmatically adding rolesProgrammatically adding roles


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out