I'm trying to switch from Archetype to NC. By Archetype there is a "show/hide" button for each Element, By NC not.
Is this planned or there is other ways to achieve same behavior?
A "published" checkbox field seems to be a solution, but I want to see published and not-published elements in list in different color/opacity or something alike.
Also, having mass actions (publish/unpublish/delete) same as in the core "List View" were noooot bad.
We have no plans for adding a disabled/unpublished feature for NC list items.
(On a side-note, our goal isn't to reproduce all of Archetype's features. If Archetype does something better, then please do consider using it - it's not an either/or situation, they both play happily together)
Out of curiosity, have you considered using regular Umbraco child nodes? This would solve the problem at hand and probably save a few headaches for your content-editors?
Hi Lee!
I'm very impressed with Nested Content, and I think this is really good alternative to Archetype. And all what I want comes from my real daily needs and I'm 100% sure that it would be useful not only for me. Temporary show/hide elements seems like a normal workflow by content management.
Using regular Umbraco child nodes can be a best solution if I can have many nested lists for each document type, separated by tabs, but this is impossible now and it'not clear if this will be implemented in future. For example, I have a document type, that embedds three different lists of different subtypes, and for my editors it would be a clear pain to manage all of these sublists in one place.
From other side, Nested Content as representation of data blocks, that are not included in main document tree is an interesting feature too.
Lee, I really love NestedContent and I just share my opinions and wishes. If they help to get NC better I'll be happy. if not, just ignore them :-)
Couldn't you just have a checkbox on your NC doc type for "Show/Hide"? Then when you render the items on the front end, only show ones that are visible?
If you need to let the back office user know if they are visible / hidden, then make it part of the nameTemplate "{{name}} {{visible}}".
As Lee said, NC has no intentions of implementing everything Archetype does, NC is intended for simple lists of complex data. If you need complex behaviors, then Archetype might be a better fit.
Hi Matt!
Yes, this was my first idea (see first post). And I will do so, when there is no other solutions.
I like NC approach to use standard umbraco document types. I wrote simple mapping between IPublishedContent and my own model, so I have something like ActiveRecord. Now I can work with Umbraco Documents and NC Records almost in the same way.
Show/Hide Nested Content Items
Hi!
I'm trying to switch from Archetype to NC. By Archetype there is a "show/hide" button for each Element, By NC not.
Is this planned or there is other ways to achieve same behavior?
A "published" checkbox field seems to be a solution, but I want to see published and not-published elements in list in different color/opacity or something alike.
Also, having mass actions (publish/unpublish/delete) same as in the core "List View" were noooot bad.
Thank you again for awesome project!
Hi Leo,
We have no plans for adding a disabled/unpublished feature for NC list items.
(On a side-note, our goal isn't to reproduce all of Archetype's features. If Archetype does something better, then please do consider using it - it's not an either/or situation, they both play happily together)
Out of curiosity, have you considered using regular Umbraco child nodes? This would solve the problem at hand and probably save a few headaches for your content-editors?
Cheers,
- Lee
Hi Lee! I'm very impressed with Nested Content, and I think this is really good alternative to Archetype. And all what I want comes from my real daily needs and I'm 100% sure that it would be useful not only for me. Temporary show/hide elements seems like a normal workflow by content management.
Using regular Umbraco child nodes can be a best solution if I can have many nested lists for each document type, separated by tabs, but this is impossible now and it'not clear if this will be implemented in future. For example, I have a document type, that embedds three different lists of different subtypes, and for my editors it would be a clear pain to manage all of these sublists in one place.
From other side, Nested Content as representation of data blocks, that are not included in main document tree is an interesting feature too.
Lee, I really love NestedContent and I just share my opinions and wishes. If they help to get NC better I'll be happy. if not, just ignore them :-)
Couldn't you just have a checkbox on your NC doc type for "Show/Hide"? Then when you render the items on the front end, only show ones that are visible?
If you need to let the back office user know if they are visible / hidden, then make it part of the nameTemplate "{{name}} {{visible}}".
As Lee said, NC has no intentions of implementing everything Archetype does, NC is intended for simple lists of complex data. If you need complex behaviors, then Archetype might be a better fit.
Matt
Hi Matt! Yes, this was my first idea (see first post). And I will do so, when there is no other solutions.
I like NC approach to use standard umbraco document types. I wrote simple mapping between IPublishedContent and my own model, so I have something like ActiveRecord. Now I can work with Umbraco Documents and NC Records almost in the same way.
Thank You.
is working on a reply...