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.0User Level Deny AccessUser Level Deny Access
Previous
 
Next
New Post
10/17/2007 4:05 PM
 

Very well documented workaround for this.

The only thing I see wrong with it is the fact that since it is a core modification you have to re-do the modification before you can upgrade in the future.

I hope that we can get this functionality as part of the core at sometime in the future.  Additionally for role level as well.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
10/17/2007 4:21 PM
 

mitchel.sellers@gmail.com wrote

I hope that we can get this functionality as part of the core at sometime in the future.  Additionally for role level as well.


I would much prefer this as part of the core as well.

I can get my hack working for roles on the tab, as well. It just requires more code modifications. And since I haven't understood why would you need to Deny a role access to a Tab (Wouldn't just not giving it the view setting work?) I didn't set it up to work with roles.
As for modules, yes, role deny would be fantastic, if I find a 'easy' hack like this for modules, I will be trying to make it role deny as well.

 
New Post
10/17/2007 4:36 PM
 

The justfication for a "deny" role has been explained to me like this.

All registered users should be able to view the page. (View to "registered users"), however members that have subscribed to the site should NOT see this page (Deny to "subscribers")

Since all subscribers are registered users, you have to deny access....


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
10/17/2007 4:45 PM
 

mitchel.sellers@gmail.com wrote

The justfication for a "deny" role has been explained to me like this.

All registered users should be able to view the page. (View to "registered users"), however members that have subscribed to the site should NOT see this page (Deny to "subscribers")

Since all subscribers are registered users, you have to deny access....

Ahhh, that makes sense.

Let's see what modifications it takes to do that. I don't expect too many, and it will remove the modification to Permissions.vb...

 
New Post
10/17/2007 6:07 PM
 

I do have role and User deny working.  I noticed a couple errors in this write up.

I'm doing a nicer write up and will post that with the updated code when I'm done.

My Write up can be found at

http://www.dotnetnuke.com/Community/Forums/tabid/795/mid/2108/threadid/177339/scope/posts/Default.aspx#177339

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0User Level Deny AccessUser Level Deny Access


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