For the content picker user control, it'd be really nice to be able to be able to specify a start node in the field configuration (as per the regular Umbraco content picker configuration).
Thanks :) well you could add your own property field types so a content picker with start node would be a nice option, I've never set the start node but if you look at the sourcecode for the default umbraco contetn picker you should be able to find out how to do it ...
No worries. We use start nodes quite a bit as we have a structured metadata library section in our content tree – essentially, a library of a large number of different types of data which are shared and aggregated in different ways throughout the site. Start nodes / restriction by content type is handy for this situation where you just want the user to be able to select content of type X from this library.
That's a very good point and a naivety in my feature request – hardcoded node ids aren't going to work in anything other than rather limited situations.
I'll cogitate and if I come up with a solution which I think may be useful for others, I'll create a pull request.
Filtered content picker
Hi Tim,
Brilliant package. Saved my bacon!
For the content picker user control, it'd be really nice to be able to be able to specify a start node in the field configuration (as per the regular Umbraco content picker configuration).
What do you think?
M
Comment author was deleted
Thanks :) well you could add your own property field types so a content picker with start node would be a nice option, I've never set the start node but if you look at the sourcecode for the default umbraco contetn picker you should be able to find out how to do it ...
Here are details on how to add your own property field types to ui-o-matic http://uiomatic.readthedocs.io/en/latest/04.CustomPropertyViews/
No worries. We use start nodes quite a bit as we have a structured metadata library section in our content tree – essentially, a library of a large number of different types of data which are shared and aggregated in different ways throughout the site. Start nodes / restriction by content type is handy for this situation where you just want the user to be able to select content of type X from this library.
Comment author was deleted
Ok I see :) well it would be a nice feature but currently have limited time so I won't be able to dev this but always open to pull requests!
Comment author was deleted
But seems it's pretty simple https://our.umbraco.org/forum/umbraco-7/developing-umbraco-7-packages/52922-dialogService-define-startnode
Only downside is that the node id has to be hardcoded so when moving between environments that might be an issue
That's a very good point and a naivety in my feature request – hardcoded node ids aren't going to work in anything other than rather limited situations.
I'll cogitate and if I come up with a solution which I think may be useful for others, I'll create a pull request.
Thanks!
is working on a reply...