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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Prevent certain admins editing a modulePrevent certain admins editing a module
Previous
 
Next
New Post
7/13/2010 9:41 AM
 
Hello all - been searching around and trying various options for this, but not found a solution. Hope you can help!

I have a module(s) shared across all pages that I only want some of our admins to be able to edit, regardless of whether they can edit the rest of the page.  I've tried / considered:
  1. Adding a 'Deny' permission to the module for the user I'd like to prevent editing - that seems to be ignored (they can still edit), despite 'Deny' apparently overriding 'Allow' permissions. The comment from Sebastian Leupold in this thread suggests that Module edit permissions are overridden by Page edit permissions (stupidly), which would prevent this from working.
     
  2. Deleting the edit permission for the Administrators role for this module from the ModulePermission table - no effect and is restored next time the module settings are edited.  Guess same reason as above?
     
  3. Adding a new admin role with limited edit permissions - not tried, but guess would again fail for above reason (if user can edit page, it seems they can edit all modules on it, including shared modules) and would be bit of a pain because would need to look into assigning new page edit permissions to this role automatically (via Default.page.template?)
So is it true that DNN permissions are so very limited that Module edit permissions can't override Page edit permissions?  And if so, is there a workaround for my (presumably not uncommon) situation?

Many thanks,  Ben

 
New Post
7/13/2010 5:34 PM
 
This is the HTML module, BTW, in case it makes a difference.

The DNN edition comparison includes the following, which further suggests that Module edit permissions are limited in the Community edition:

Granular Permissions
Page, module and folder level extended permissions provide granular security rights which allow you to precisely define which content contributors can edit which modules on each page.
If this is the case, has anyone tried Oliver Hines' Enhanced Permissions Provider?  It looks excellent, but I'm concerned by the fact that it hasn't been updated since Feb 09!

Suggestions + comments welcome!
 
New Post
7/13/2010 7:42 PM
 
I believe you're correct about the problem, but what about making those accounts not admins? Afterall, admins should be able to do anything on the site. If you made subgroups and gave people permissions to certain areas this would be no problem at all. (you can also give people permissions to certain parts of the admin menu even if they aren't admins).
 
New Post
7/14/2010 5:47 AM
 
Hi Mike - that's option #3, but I don't think it solves the problem - I want my page editors to be able to edit all pages, but not this particular module. Until now, I thought DotNetNuke was up to the job, but looking at the (completely over-priced for our needs) Pro spec sheet, it looks like the Community version has been crippled and this functionality reserved for Pro only.

Jesus, you don't get this with Joomla, Drupal, WordPress, et al, which are also free open source products. When I find out that basic functionality like this has been reserved for the commercial version, it makes me question whether I've picked the right CMS. I can't understand why DNN Corp need to keep key features like this (and approval workflow) from the Community version - surely things like support, documentation and indemnity are enough to distinguish it.

>:(
 
New Post
7/14/2010 12:36 PM
 
Ben, this is expected behavour - admins are admins and cannot revoked any permissions by definition atm (years ago I created a configurable permission grid and donated it to DNN Corp, but it was not accepted). I agree, that there is some need to overhaul the UI and display properly, how some permissions cannot be revoked or granted.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Prevent certain admins editing a modulePrevent certain admins editing a module


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