previous blog post, I wrote about my frustration with the Nested Content plugin due to my unique requirements for my current project. However, as I have learned more about Umbraco I have discovered a better way to implement a solution with built-in Umbraco.
##Instead of Nested Content control, just create child nodes using List View.
The main reason for using the Nested Content control was because we liked the user experience when adding child nodes to the parent node but as described in my previous post unfortunately Nested Content doesn’t create real nodes as I initially thought. So to get a decent user experience we decided to use the a ListView property editor for the children nodes. This way they are created as real Umbraco nodes and then I can use an Umbraco Relation to associate the child node(s) to the Umbraco Member account.
###How to use ListView property instead of Nested Content
This might be something that is really easy to understand for more experienced Umbraco developers but I decided to describe the steps I used in case someone else has a similar problem and is new to Umbraco.
Add a property
Select the ListView editor
Setup the ListView property (default name is DocuentType - PropertyName - PropertyType)
Submit the property
Set Parent’s DocumentType Permissions
Choose Child’s DocumentType
Notice Child’s DocumentType is added
Now you can add children via ListView’s Create option
Would enjoy discussing with you a different way to solve this problem! Sound off in the comments below or reach out to me via Twitter or LinkedIn!
"/>
previous blog post, I wrote about my frustration with the Nested Content plugin due to my unique requirements for my current project. However, as I have learned more about Umbraco I have discovered a better way to implement a solution with built-in Umbraco.
##Instead of Nested Content control, just create child nodes using List View.
The main reason for using the Nested Content control was because we liked the user experience when adding child nodes to the parent node but as described in my previous post unfortunately Nested Content doesn’t create real nodes as I initially thought. So to get a decent user experience we decided to use the a ListView property editor for the children nodes. This way they are created as real Umbraco nodes and then I can use an Umbraco Relation to associate the child node(s) to the Umbraco Member account.
###How to use ListView property instead of Nested Content
This might be something that is really easy to understand for more experienced Umbraco developers but I decided to describe the steps I used in case someone else has a similar problem and is new to Umbraco.
Add a property
Select the ListView editor
Setup the ListView property (default name is DocuentType - PropertyName - PropertyType)
Submit the property
Set Parent’s DocumentType Permissions
Choose Child’s DocumentType
Notice Child’s DocumentType is added
Now you can add children via ListView’s Create option
Would enjoy discussing with you a different way to solve this problem! Sound off in the comments below or reach out to me via Twitter or LinkedIn!
In a previous blog post, I wrote about my frustration with the Nested Content plugin due to my unique requirements for my current project. However, as I have learned more about Umbraco I have discovered a better way to implement a solution with built-in Umbraco.
##Instead of Nested Content control, just create child nodes using List View.
The main reason for using the Nested Content control was because we liked the user experience when adding child nodes to the parent node but as described in my previous post unfortunately Nested Content doesn’t create real nodes as I initially thought. So to get a decent user experience we decided to use the a ListView property editor for the children nodes. This way they are created as real Umbraco nodes and then I can use an Umbraco Relation to associate the child node(s) to the Umbraco Member account.
###How to use ListView property instead of Nested Content
This might be something that is really easy to understand for more experienced Umbraco developers but I decided to describe the steps I used in case someone else has a similar problem and is new to Umbraco.
Add a property
Select the ListView editor
Setup the ListView property (default name is DocuentType - PropertyName - PropertyType)
Submit the property
Set Parent’s DocumentType Permissions
Choose Child’s DocumentType
Notice Child’s DocumentType is added
Now you can add children via ListView’s Create option
Would enjoy discussing with you a different way to solve this problem! Sound off in the comments below or reach out to me via Twitter or LinkedIn!
