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.0Cache & User RolesCache & User Roles
Previous
 
Next
New Post
5/29/2007 7:34 PM
 

That worked like a charm.  Thanks for posting it - it was driving me crazy!

-Scott

 
New Post
9/7/2007 4:21 PM
 

I've been working on the issue of getting the cache to clear after programatically adding a role to the logged in user.  I found the the code you posted above (along with a few variations of it on a few other posts). 

Response.Cookies("portalroles").Value = Nothing
Response.Cookies("portalroles").Path = "/"
Response.Cookies("portalroles").Expires = DateTime.Now.AddYears(-30)

I got excited because it works beautifull on my development laptop.  The issue is once i moved the code to the development server in my office the cache stopped clearing and the page i directed the user too now gets a "you dont have access...." message.   Its the same code.... you wouldn't have any idea why this is?  Is this a configuration thing on the server or within DNN config that would make it work one place and not the other. 

I also found some code in another post to actually "log out and log in" the user on the fly,  but this gave the same results. 

I'm hitting a wall,  all i want to do is assign a new role to the current logged in user (from my custom module) and then redirect them to a page that that role has access too.

Please help if you or anyone else can. 

 

 
New Post
9/8/2007 6:34 AM
 

It did seem to be working fine for me during development.

But the moment we pushed the site live the cache problem came racing back.

This really is a very poor state of affairs IMHO.

I too would appreciate some assistance or guidance on this one.  Been
beating head against brick wall for way to long.

Westa

 
New Post
2/11/2008 8:10 PM
 

I've had this same problem intermittently for a while. I've been through the forums here for help but just found that lots of us have the issue. So I decided to debug myself. Likewise for me, all works well in my dev environment, but not on QA and production. I believe I've found the issue and I've put in a bug report. I'd bet in your dev environment you run your database server on the same machine as your web server and in your live environment they are on separate machines. Take a look at http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=7070&PROJID=23. I put my workaround in there. If that doesn't work for you, after you understand the problem, you'll probably be able to come up with another.

One final note: You still need to clear the "portalroles" cookie and the user cache sometime between adding the new role and redirecting to a page that requires the new role. The following two lines of code will do it:

         DotNetNuke.Security.PortalSecurity.ClearRoles();
         DataCache.ClearUserCache(PortalId, Username);

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Cache & User RolesCache & User 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