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 ...Default Page PermissionsDefault Page Permissions
Previous
 
Next
New Post
10/11/2011 10:34 PM
 
I have two roles used to restrict access for 'unlinked' users to a specific page, which requests a 'link' so to speak. The rest of the pages are all accessible to 'linked' users. This is obviously easy to perform using roles and page permissions, but I want to ensure that new pages added are accessible to 'linked' role and denied to 'unlinked' role by default. Currently no permissions are set by default. Is there a way to customise this default setting? Do I need a module to do this?

Thanks
 
New Post
10/12/2011 5:18 PM
 
I have been looking for an answer to this as well. This would be very handy for the way we produce websites and restrict options for different user levels.

Any info would be great!

Jeremy
 
New Post
10/13/2011 11:03 AM
 
you can do this via page templates - http://www.dotnetnuke.com/Resources/W... . If you don't want to select a different template each time you can also edit the default template which can be found at Portals\0\Templates\Default.page.template .Please note it only shows a page with default permissions but modules with custom permissions, but the UserProfile.page.template in the same folder shows an example of both page (tab) and module permissions

The easiest way to do this is to create a new page, set your permissions, add any relevant module(s) and set their permission(s) and then export that as a page template - now copy the contents of that file into the default.page.template and you should be good.

Cathal

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
10/13/2011 11:27 AM
 
Ok, this input is great, but it doesn't seem to be working.I have made changes to my default.page.template file both at the portal 0 level and at the _default level, and it is not having any affect on page permissions or skin choice. The only permissions that are set is All Users can View.

I have 2 custom roles that should also have view and/or edit permissions at the page level.I have added a <permission> node at the <tabpermission> level, as well as some in a basic HTML/Text Module. I also added a skin to use instead of the site default. None of this seems to be applying.

I am using DNN 6.0.2 Community Edition.

Thanks,
Jeremy

*Edited for clarity and more info.
 
New Post
10/13/2011 11:38 AM
 
After some additional testing, I have noticed a few more details:

Module settings work just fine, title, permissions, etc.

Nothing at the page/tab level are being applied, permissions, skin.

I would love to be able to have all these settings pre-configured so that end users simply select the appropriate template and don't have to leave the main tab of Add Page, or can even use the Add new page feature in the tool bar.

Thanks,
Jeremy
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Default Page PermissionsDefault Page 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