I suggest that should change umbracoNaviHide as umbracoNaviShow
because most of time, every item of navigator has a lot of items should set as umbracoNaviHide=0, if use umbracoNaviShow, it's no need to set, I think every Navi item must has more than one item for most of people, so this is worth to change.
If you change it as I say, I think more people can use modules for runway directly, no need to modify. And this part of people are more than some people need umbracoNaviHide.
My understanding of 'umbracoNaviHide' is that you would use it with a 'true/false' (data-type) checkbox property in your document-type. By default the value is 'false', meaning that a page (content node) is visible (when published). In order to 'hide' the content page, you set the value to 'true' (on a page-per-page basis).
By swapping this logic around to use 'umbracoNaviShow' are you suggesting that content pages are hidden by default? and you can enable them on a page-per-page basis? That seems like a lot more work for the CMS editors.
I suggest that should change umbracoNaviHide as umbracoNaviShow
because most of time, every item of navigator has a lot of items should set as umbracoNaviHide=0, if use umbracoNaviShow, it's no need to set, I think every Navi item must has more than one item for most of people, so this is worth to change.
this depends from site to site, you are always free to change it on your own implementation.
If you change it as I say, I think more people can use modules for runway directly, no need to modify. And this part of people are more than some people need umbracoNaviHide.
Hi sun,
My understanding of 'umbracoNaviHide' is that you would use it with a 'true/false' (data-type) checkbox property in your document-type. By default the value is 'false', meaning that a page (content node) is visible (when published). In order to 'hide' the content page, you set the value to 'true' (on a page-per-page basis).
By swapping this logic around to use 'umbracoNaviShow' are you suggesting that content pages are hidden by default? and you can enable them on a page-per-page basis? That seems like a lot more work for the CMS editors.
Unless I am misunderstanding your suggestion?
- Lee.
For most of sites, news are more than menu, structure will like this:
homepage
--menu1
----lots of news(no need show on navigator.
--menu2
----lots of news(no need show on navigator.
if you use umbracoNavHide, you will have to set many news as fault.
if you use umbracoNavShow, you will not need to set value.
I can change it by myself, But I just want more basic users can use a pesonalize runway.
In this case I'd suggest that you simply filter out news items from your navigation based on type
is working on a reply...