Hi all,

I've posted a patch relating to the following:
http://www.codeplex.com/umbraco/WorkItem/View.aspx?WorkItemId=16324

Basically doing this was due to a client asking us for this functionality but we've had a few clients now asking about this too so hopefully if anyones been asked about these things, you can have a fix for them.

- Assigning browse permissions to content tree nodes so the user has access to update child nodes but not parent nodes
- Ability to have the publish to button available to other users other than just "reader"
- Context menu customization

This patch addresses all of these things and I've documented everything in the patch in regards to changes, etc...

One cool part about the R&D for creating this patch is I've managed to open up a potentially really cool feature of Umbraco developers which would allow them to create their own custom Actions and assign their own custom Action handlers to them and then even put these actions in the context menu. Its actually really simple to do.

I've fixed up a bunch of code in the standardTreeFunctions file for the content tree and have added a more robust way to manage trees by inheriting from the new BaseTree class (there's alot of strings hard coded to create these trees and this will avoid having to do this for setting attributes). I've also fixed up a few potential bugs in other files. The full details are in the change log in the patch.

If anyone has feedback, i'd love to hear it! I'm hoping that these changes can be used for newer verions of Umbraco.

patch is here:
http://www.codeplex.com/umbraco/SourceControl/PatchList.aspx

Hi Shandem

Thanks for the patch, will look into and see what changes you made, but from your post it sounds cool.

It really touches on the oldest, and probably the single most hacked element in umbraco - the tree. And I think the entire core team really wish that we could just take it out back and shoot it in the head, and replace it with some nicer and cleaner code, but unfortunately it won't be for any of the 3.X releases, it will have to wait for the 4.0 which will be a big refactor of how umbraco handles the tree, applications, actions etc.

So we hear you loud and clear, the tree should get better, but as of now, too many things depend on it, so we will not risk the stability and backward compatibility of the 3.X branch to make those big changes to the core.

---

Umbracian

Yeah, i'd be more than happy to work closer with the team. We use Umbraco for quite a few websites and we're always having clients asks us for additional features which we're just now starting to look into. If you want to let me know how/what/when/where you'd want me to help out, I'm all ears.
I'd be happy to look at fixing up more of the tree functionality if no one else has looked at doing this yet...