Adding/Editing Pages

This forum is primarily for reporting issues about Web Accessibility such as difficulty using mojoPortal with a screen reader or other assistive technology.

Post any feedback here related to improving the accessibility or usability of mojoPortal. As stated in our Accessibility documentation, it is an important goal of the project that both the front-end customer experience and the back end administration and content publishing features be accessible to as many people as possible. Ideally, if you post about problems, we will also be glad to have suggestions on how the problems can be fixed but all constructive feedback on these issues is welcome.

This thread is closed to new posts. You must sign in to post in the forums.
6/2/2009 5:02:26 AM
Total Posts 29

Adding/Editing Pages

I notice that the parent page menu (when adding or editing pages here: /Admin/PageSettings.aspx) does not list pages that are not included in the menu. For example, I told the homepage not to show on the menu since the banner in my skin is a URL to it, however when I want to add a new page, that is "below" the home page, I have to temporarily allow Home to be showed in the menu so I can add the new page below it. Of course it is not a big deal, as I can work around it, was just pointing it out. I noticed that all the pages can be listed here: /Admin/PageTree.aspx, so I was wondering why the same couldn't be done on the page settings page.

6/2/2009 5:22:17 AM
Total Posts 18439

Re: Adding/Editing Pages


I've debated about this with myself as its also a usability issue if you make it easy for a user to create a page that might be invisible. Then I will be answering posts about why did my new page disappear?

See, if the child page is not in the same menu then it will appear but if its in the same menu it will not be visible if you create a benenath another page that is not visible in the menu. Many of the skins have split menus where the top menu is horizontal and only shows one level and there is a PageMenu that starts at one level beneath it. So in this case you can make home invisible and its children would show because of the split menu, but if the parent page is already in the lower menu or if you use a skin that does not split the menu or any skin where the child page is in the same menu as the parent, the child page would not be visible. To me this would be more of a support issue than the occasional person noticing that they have to make a page visible before adding child pages beneath it. To me it seems like its better that an extra step is required before you can make a child page beneath an invisible page, at least this way its clear to the user that the page they are trying to use for the parent is not visible.



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