If you have questions about using mojoPortal, you can post them here.
You may want to first review our site administration documentation to see if your question is answered there.
On some mojoPortal sites, the Parent Page property on page settings is a drop-down list, on others there is a "browse" link that opens a tree view.
How is this determined? I can't see anything obvious in the skin or web.config.
Why am I asking? Because the site I'm working on is in "browse" mode, and it takes me about 6 clicks to expand the browser to the page I want to set as the parent, and I need to do this for a lot of pages :-(
So I want to switch to DDL mode.
>> Request: if there was a way of expanding all nodes in the browse tree view that would make me happy too.
>> More ambitious request, but what I really want... drag and drop in the Add/Edit Pages tool.
By default if the site has > 150 pages the dropdown is not used. While it is technically possible for you to override that threshold, in practical terms you really should not because what happens when there are more is that there will be an error when saving the page due to too many form elements on the page. This problem was introduced by a security update to asp.net a long while back that set a limit on the number of form elements allowed for postback. People with large sites started getting errors so we came up with the dialog page for sites with a lot of pages. Same thing with roles and permissions, if there are lots of roles we have to use separate pages to avoid errors due to too many elements when there is a large checkbox list along with all the other form elements in a page.
Hope that helps,
Thanks that explains it.
However, we really find moving pages around very laborious with the popup tree view because of all the expanding and scrolling that has to be done.
Any thoughts on my feature requests?
>> a way of expanding all nodes in the browse tree view (perhaps just open it with all expanded). This would stop all the click > delay > scroll down again > click > delay > scroll down again etc etc.
Put this in your user.config:
<add key="ParentPageDialogExpansionDepth" value="-1"/>
after the next release that will make it fully expanded on the parent page dialog. I just implemented it so it won't do anything until the next release.
Thanks Joe - will do, and this will help.