We are in the process of developing a site where we have a page that contains a list view. We are using the list view to provide a way for the client to easily manage a section of the page that needs the same group of content.
For example, we have a services list. Each list item must have an image, a title and a description. This provides a simple way for the client to add as many services to the page without us having to go back and edit the document type.
Our problem is 2 fold. The first is that we do not want them list items to show up in the navigation (content tree). They are simply repeatable items on the services page. Is there a setting to do this?
The second problem we are facing, is that when we add a subpage (even using a different document type) under a page with a listview, the new subpage is being added to the listview. Which in our sernario, the new subpage is being included as a service item. This one is rather frustrating as it makes no sense to have a subpage item being added to a listview.
Is there a different option to accomplish this without using the listview?
Hi Jeremy.
If you select list view for a page every child will be displayed in the list view, no matter what doctype they are, this is how the list view it works. It would be a nice feature to have specific doctypes showing up in the list view and the rest in the Content tree as nodes, however this is not possible right now.
What you could do, is having a container for your services, like "Services", that you enable list view for, and under that node you create all your services. And your page doesn't have list view enabled. That way services will display in a list, and all the other doctypes won't.
However a even better option, in my opinion, is having a look at Nested Content. From what you are describing, it sounds like Nested Content would be a perfect fit for your project. That way you could create Services as components on a page, and not an actual child node. Don't worry if you've already built a lot, Nested Content build upon Document Types so it's really easy to rebuild an existing site to use NC and you won't need to trash your existing doctypes.
Page with a List View and Subpages
We are in the process of developing a site where we have a page that contains a list view. We are using the list view to provide a way for the client to easily manage a section of the page that needs the same group of content.
For example, we have a services list. Each list item must have an image, a title and a description. This provides a simple way for the client to add as many services to the page without us having to go back and edit the document type.
Our problem is 2 fold. The first is that we do not want them list items to show up in the navigation (content tree). They are simply repeatable items on the services page. Is there a setting to do this?
The second problem we are facing, is that when we add a subpage (even using a different document type) under a page with a listview, the new subpage is being added to the listview. Which in our sernario, the new subpage is being included as a service item. This one is rather frustrating as it makes no sense to have a subpage item being added to a listview.
Is there a different option to accomplish this without using the listview?
Hi Jeremy. If you select list view for a page every child will be displayed in the list view, no matter what doctype they are, this is how the list view it works. It would be a nice feature to have specific doctypes showing up in the list view and the rest in the Content tree as nodes, however this is not possible right now.
What you could do, is having a container for your services, like "Services", that you enable list view for, and under that node you create all your services. And your page doesn't have list view enabled. That way services will display in a list, and all the other doctypes won't.
However a even better option, in my opinion, is having a look at Nested Content. From what you are describing, it sounds like Nested Content would be a perfect fit for your project. That way you could create Services as components on a page, and not an actual child node. Don't worry if you've already built a lot, Nested Content build upon Document Types so it's really easy to rebuild an existing site to use NC and you won't need to trash your existing doctypes.
https://our.umbraco.org/projects/backoffice-extensions/nested-content/
Good luck on your project!
Take care!
Dennis
is working on a reply...