2

Closed

Enh: Improve distributility

description

currently the module alwass grant access to the full site structure.
It would be great, if an admin could specify a root page in module settings, and only pages beneath can be managed with current instance of the module.
This would allow the module to be used by "content managers" for just a branch of the site.
Closed Jan 27, 2011 at 8:11 AM by proeder

comments

proeder wrote Nov 6, 2010 at 10:03 AM

I eas thinking of that already. Trouble is, when you edit a page you can always move it to another position (by using the parent page dropdown)

proeder wrote Nov 6, 2010 at 10:14 AM

That would be a conflict with your other issue to remove publish rights by default, wouldn't it?

leupold wrote Nov 6, 2010 at 11:05 AM

You need "create child pages" permission (mapped to "edit page" permission in CE permission provider) for the parent page to select it - otherwise this would be an issue of the core framework, which needs to be fixed. Of course, admins need to grant publish permission to themselves, but for being this an edge case, I'd still prefer the list of available modules not being bloated with all the rarely used items.

lucasjans wrote Dec 18, 2010 at 2:34 PM

Let me get this right: You want to share this module with site editors, but don't want them to modify/view pages that they don't have access to?

I think it would be great if this module detected the login users permissions and only display the pages they have access to change the parent page of (mirroring the dnn core settings, and being cognizant of DNN Professional permissions.)

wrote Dec 22, 2010 at 3:44 PM

proeder wrote Jan 27, 2011 at 8:11 AM

The ability of setting the root page is now a setting

wrote Jan 27, 2011 at 8:11 AM

wrote Jan 27, 2011 at 8:11 AM

wrote Feb 13, 2013 at 6:12 PM

wrote May 15, 2013 at 3:51 AM