search

umbraco / Umbraco-CMS

Umbraco is a free and open source .NET content management system helping you deliver delightful digital experiences.
https://umbraco.com
MIT License
4.49k stars 2.69k forks source link

MultiNodePicker with support for creating new nodes #9655

Closed nzdev closed 2 years ago

nzdev commented 3 years ago

Add support for creating new nodes from the multi node picker, so that if no node exists, you can then use the infinite editor to create the node.

joepvtl commented 3 years ago

Hi,

Yes! We also would like this to be in the core. We already have some custom code to support infinite editing for ContentPickers and MNTP. If the core team would be interested in this, we could make a PR to implement this.

nul800sebastiaan commented 3 years ago

I think MNTP is pretty much legacy at the moment so I doubt we'd spend a lot of time getting that properly updated. Content pickers might be feasible. I'll discuss at HQ in and will get back to this.

liam-coghill commented 3 years ago

Yes! The QoL improvement for content editors this would bring makes it pretty valuable in my opinion. We often get content editors complaining about this. And we're often faced with the difficult decision between MNTP and NestedContent when it's unclear how often the content is going to end up being reused.

@nul800sebastiaan when you say you think MNTP is pretty much legacy right now, is there something we should be using instead? I'm wondering if I'm missing something because the Content Picker in v8.11.1 doesn't support multiple items as far as I can tell? We almost solely rely on MNTP even for single item pickers to make use of the xpath start node and to only allow certain document types to be selected.

umbrabot commented 2 years ago

Hiya @nzdev,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face: