I've got an umbraco site where many (90%) of the users have a membership login and update the content through a series of simplified forms/ui rather than the full umbraco interface (which is used more by senior administrators).
However there is one thing that I'd like to isolate and make available and it's essentially a custom tree section, so a section of content could be shown as a tree view in a normal web page to a logged in member, and then have some simple actions to create & edit (to my own simplified form), move & sort (ideally i'd like to resuse the existing function for this).
It feels like this should be possible, and maybe quite straightforward, but... is it? not really sure where to start, any hints or tips greatly appreciated :)
I think that uWebshop does something similar. They have a custom tree, but it are real Umbraco nodes which they just hide in the content section and show in the custom section. So it should be possible :).
thanks Jeroen - I've tried the uWebShop one - but this appears in the Umbraco back office as an additional section, do you think this could this be part of a regular web page? could i just implement a control (maybe an ascx) that uses it as a standalone without being part of the backoffice?
I haven't seen or used uWebshop but there is really not much difference in user controls used in the back office or on the publicly visible section of the site. The difference is in how you wrap or reference the user control
To put a user control onto the publicly visible area of the site you simply wrap it in a macro and drop this onto a template or directly onto the page. Whereas to use it as a dashboard in the backend you add some xml to the dashboard.config file in the config folder. The underlying user control is the same.
So if you can write your tree control (which should be straight forward as you say) you can put it anywhere you like.
Using Tree View in Web Site
I've got an umbraco site where many (90%) of the users have a membership login and update the content through a series of simplified forms/ui rather than the full umbraco interface (which is used more by senior administrators).
However there is one thing that I'd like to isolate and make available and it's essentially a custom tree section, so a section of content could be shown as a tree view in a normal web page to a logged in member, and then have some simple actions to create & edit (to my own simplified form), move & sort (ideally i'd like to resuse the existing function for this).
It feels like this should be possible, and maybe quite straightforward, but... is it? not really sure where to start, any hints or tips greatly appreciated :)
I think that uWebshop does something similar. They have a custom tree, but it are real Umbraco nodes which they just hide in the content section and show in the custom section. So it should be possible :).
Jeroen
thanks Jeroen - I've tried the uWebShop one - but this appears in the Umbraco back office as an additional section, do you think this could this be part of a regular web page? could i just implement a control (maybe an ascx) that uses it as a standalone without being part of the backoffice?
Sorry I don't know. I've created custom trees before, but only in the backoffice. It's probably possible somehow, but I can't help you with that.
Jeroen
Hi John,
I haven't seen or used uWebshop but there is really not much difference in user controls used in the back office or on the publicly visible section of the site. The difference is in how you wrap or reference the user control
To put a user control onto the publicly visible area of the site you simply wrap it in a macro and drop this onto a template or directly onto the page. Whereas to use it as a dashboard in the backend you add some xml to the dashboard.config file in the config folder. The underlying user control is the same.
So if you can write your tree control (which should be straight forward as you say) you can put it anywhere you like.
well that's encouraging enough to have a go...
i was just wondering if there would be any dependencies that would be required outside the backoffice that i'd need to support
is working on a reply...