I have a number of placeholder pages marked - Is Draft = Checked 

My Expectation was that these would then not show up in the Child page site map however I logged in as a User account and was surprised to see them there, while the page shows no content if clicked through I would have thought that draft pages would not show up in the child page site map.

If I am missing something let me know 

Thanks as always 

Al 

Joe A 

Thanks for the quick response

I have a test account that is a member of a custom group called customers which matches our corresponding AD group (LDAP)

The pages are showing in the child page site map and when clicked are accessible but with no content. If I understand correctly then they should not been seeing these pages listed.

Could I be missing something else?

Al

Joe

I checked again after ensuring that I had cleared the cache and the problem persists

• Its is a root level site 
• Running in a virtual directory http://support.tsaadvet.com/supportportal/default.aspx
• LDAP authentication 
• MSSQL 2008
• IIS 6
• v2.3.5.8 running under .NET v3.5

Let me know if you need any additional information and sorry about the delay in responding 

Thanks as always

Al

I've known all along that draft pages were only visible when one was logged in.  It so happened that the users who saw them were always in either Administrator, Content Administrator, Content Publisher, or Content Author roles. 

However, just today I stumbled upon a case where we had a custom role defined which was checked under "Roles that can edit this page"  for a couple of draft pages and the user was not able to see the pages in the menu.

It only seems logical to make the menu nodes in SiteMenu and PageMenu controls visible for users who have edit rights for those particular draft pages.

So in case like this:

- Parent (draft) (include in menu: true)
-- Child 1 (draft)  (include in menu: true)
-- Child 2 (draft)  (include in menu: true)
-- Child 3 (draft)  (include in menu: true)

Provided that the user has edit rights for all four pages and all four are marked to be included in the menu, the user should see them in the menu.

And in this case: 

- Parent (draft) (include in menu: false)
-- Child 1 (draft) (include in menu: true)
-- Child 2 (draft) (include in menu: true)
-- Child 3 (draft) (include in menu: true)
 
When user goes to one of the three child pages, he/she should be able to see the other two, but never the parent. 

Similar behavior would be expected in places like Site Map as well.

Thoughts?

Well that depends on the menu structure. If the user visits the parent page that is not included in the menu and the parent page has a child page menu/sitemap on it then the user should see the child pages assuming the same as above that the user is in an allowed view role and either in an edit role or draft edit role.

However, menus are hierachal, the child page menu starts binding below the parent therefore it can show the child pages even when the parent is not included in the menu, similar with PageMenu if it is configure to bind nodes starting below the parent it can show the child pages. But in any menu where the parent level is also included, the the child pages cannot be shown if the parent is not shown since the children are below the parent in the hierarchy they hang off the parent page and they cannot be shown if the parent is not there. So in a case like the site map its just a single menu with the entire site hierarchy, any page that is not included in that menu also removes the sub hiearchy below that page. ie there is no way to databind the hierarchy below the parent if the parent node is excluded from the tree structure that is the hierarchy.

I agree.  Thanks for the bug fix.  Will pull and test tomorrow morning.