Should Draft Pages show up in the Child Page site map?

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
4/12/2012 5:46:08 PM
Gravatar
Total Posts 156

Re: Should Draft Pages show up in the Child Page site map?

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.

You must sign in to post in the forums. This thread is closed to new posts.