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.0Extending the DNN Core PermissionsExtending the DNN Core Permissions
Previous
 
Next
New Post
6/15/2006 4:12 PM
 

Has anyone tried extending the core module permissions in the Permission table to allow more than just View or Edit? I have tried adding new permissions for CREATE, UPDATE and DELETE as SYSTEM_MODULE_DEFINITION's and they appear to work as expected, showing up for all modules.

I also added two "module definition specific" permissions ADDTHREAD and ADDREPLY which only show up on the Module Settings page for the applicable module(s). See codes below:

ID PermissionCode ModuleDefID PermissionKey PermissionName -- ------------------------ ------- ------------- --------------- 1 SYSTEM_MODULE_DEFINITION -1 VIEW View 2 SYSTEM_MODULE_DEFINITION -1 EDIT Edit 7 APPLICATION_MODULE_DEFINITION 94 ADDTHREAD Add Thread 8 APPLICATION_MODULE_DEFINITION 94 ADDREPLY Add Reply 12 SYSTEM_MODULE_DEFINITION -1 CREATE Create 13 SYSTEM_MODULE_DEFINITION -1 UPDATE Update 14 SYSTEM_MODULE_DEFINITION -1 DELETE Delete

This does not appear to adversely affect any of the core functionality, but it is hard to tell for sure without more extensive testing. Of course, none of this has any real affect unless code is added to the modules to check for the extended permissions

I am anxious to know if this approach has been tried before and what the results were

Thanks in advance for any feedback. Ken
 
New Post
6/15/2006 5:04 PM
 
This appears to be correct - although its a bit tough to tell with the formattiing of your permission table *grin*

Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
6/15/2006 5:06 PM
 
have a look at UserDefinedTable 3.3.0 - when source code will be available.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/16/2006 1:09 AM
 

Sorry about the table, it was a cut-and-paste. I tried to reformat in html after previewing but it wouldn't let me. Here is a, hopefully, more readable version:

ID  PermissionCode        ModuleDefID  PermissionKey  PermissionName
1   SYSTEM_MODULE_DEFINITION       -1  VIEW           View
2   SYSTEM_MODULE_DEFINITION       -1  EDIT           Edit
7   APPLICATION_MODULE_DEFINITION  94  ADDTHREAD      Add Thread
8   APPLICATION_MODULE_DEFINITION  94  ADDREPLY       Add Reply
12  SYSTEM_MODULE_DEFINITION       -1  CREATE         Create
13  SYSTEM_MODULE_DEFINITION       -1  UPDATE         Update
14  SYSTEM_MODULE_DEFINITION       -1  DELETE         Delete

 
New Post
6/16/2006 4:58 AM
 
I suggest prefixing your keys with a unique module identifier, this will leverage the effort needing on upgrades, ...

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Extending the DNN Core PermissionsExtending the DNN Core Permissions


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