reader pages and user accounts

[Ben_360fusion]

Hi,

How do people organise their reader pages?

Do you have then as a sub section of the site structure like this:
-home
-contact us
--contact us success

Or do you have a seperate site section like this

-home
-contact us
-reader pages
--contact us success
--news reader
--etc

I ask this as i create a user account called admin and then restrict this group to be only be able to see pages an admin to a website will need. in the user group account settings if you selct a top level site structure in the page mount it will automatically include all subpages.

I don't want to show these sub pages so is this an organisational issue or a feature request to change the way page mounts work?

Cheers
Ben

[Justin]

Hi, I usually put the reader pages into the sub pages like you have:

-home
-contact us
--contact us success

For me, it makes the most sense. Because there is usually only a handful of pages that I do not want other users to access, I will go into these individually and set permissions so they cannot have access. I do this by setting permissions for the owner of the page only, me :D . This will still show the page, but the other users will not be able to edit, copy, delete, etc. for those pages.

I know the icons are greyed out when the user doesn't have permissions to write to the pages. I guess there could be a feature request put in so when the user doesn't have access to the page it could be hidden. In my experience it's not a big deal if the users see the page, as long as they can't have access to edit it.

[Ben]

I do the same as Justin, where it looks like this:

- home
- news
------ reader
------ archives
- contact
------ success

[Ben_360fusion]

Yep, that's what i do too.

I may add a feature request to allow you to disable the automatic inclusion of sub levels in the page mout section of the user group settings.

This will also mean I can leave things like the news navigation under the about us section but hide it from client admin until they require it. then it's just a case of adding it to the allowed list in the page mount section.

I'm going to do a bit more playing around first.

Cheers