Hi All,

I have a situation where I have a website that is divided into sections, such as "Education", Policy and so on, each one edited by people in a different role in the Society and with a different DNN user role.

None of the page editors are administrators, they just have a role that is given Edit permission on the section home page, and all of it's children, and some shared areas.

The top page of each section, what we call the "section home page" is a top level page with no Parent Page.

I notice now that when a user in one of these roles edits the "Page Settings" for their section home page, the "Parent Page" lists only the pages they can edit directly, and NOT the option, which is, and should remain, their parent. This means that a page editor can not edit their section home page "Page Settings" without corrupting the website by moving their homepage somewhere into a shared area. I have to go in and fix it.

Is there a solution to this problem other than making all of my users administrators, and undermining the entire point of having the roles?

Thanks
Brian

Hi Sebastian,

Thanks for the swift response.

Rereading my post, it isn't quite as clear as it ought to be. This isn't really a matter of the granularity of the permissions.

The issue is that when a page actually has no parent page, and hence the Parent Page control should hold " and the Page Settings are edited by a user in a role that is not an administrator, the user in that role gets a list of Parent Pages that does not include "" , with the first item in the list selected, and hence when they update the page they change the parent page.

On this site I am on DNN 05.02.03 (74)

This site is going to be a pain to upgrade, because it's fiddly getting the new Rich Text Editor installed, and configured, so I have to make a full copy and ask quite a lot of people not to update the site for an extended period while I upgrade a copy of it, check it out, and then swap over. So while that upgrade is on the cards, I want to delay it for a little while. However, if an upgrade will fix this issue, I will reprioritize the upgrade, as I think this issue is important to resolve for my users.

Thanks
Brian