This may be wishful thinking but...I have a site that was spec'd to have a limited number of Nested Content Items for a particular doctype property. That list has now grown to in excess of 100 items and so to make it more manageable the customer is asking for the ability to filter the list on a property to make it easier to locate the items they want to edit.
I fear that the only option now is to promote the items in the list to real nodes and lose the nested content property but first wanted to check if there is any possible way of a listview style rendering of the items in the nested content property?
Yikes! :-) (if the forum had emojis, I'd put a heart ❤ here)
NC original intent was simple lists, we hadn't considered management tools for the nested data. But I understand now how these things can become overgrown.
If you're asking if it's possible to filter the NC data - yeah, sure it's not impossible - ultimately the data is JSON, but probably needs some funky Angular skills to develop it.
Personally I'd go with the "real" nodes option - feels like a more maintainable solution.
Filtering a long list of nested content items
This may be wishful thinking but...I have a site that was spec'd to have a limited number of Nested Content Items for a particular doctype property. That list has now grown to in excess of 100 items and so to make it more manageable the customer is asking for the ability to filter the list on a property to make it easier to locate the items they want to edit.
I fear that the only option now is to promote the items in the list to real nodes and lose the nested content property but first wanted to check if there is any possible way of a listview style rendering of the items in the nested content property?
Cheers and thanks for an awesome package guys!
Hi Simon,
Yikes! :-) (if the forum had emojis, I'd put a heart ❤ here)
NC original intent was simple lists, we hadn't considered management tools for the nested data. But I understand now how these things can become overgrown.
If you're asking if it's possible to filter the NC data - yeah, sure it's not impossible - ultimately the data is JSON, but probably needs some funky Angular skills to develop it.
Personally I'd go with the "real" nodes option - feels like a more maintainable solution.
Cheers,
- Lee
Thanks Lee - I thought as much but it was worth asking. FYI, your heart was visible in the notification email so all is not lost :)
I might lack the funky Angular skills and budget on this job to have a go so will promote the content into normal nodes. Thanks for the clarification.
Cheers, Simon.
is working on a reply...