U4-2747 - [Feature Request] 6.1.4 Pre-select current node it content pickers

Created by Jeremy Pyne 29 Aug 2013, 15:30:31 Updated by Sebastiaan Janssen 30 Apr 2014, 16:40:58

Relates to: U4-192

When using Move/Copy dialogs, or useing other content picker properties in our content, we end up spending lots of time just browsing out umbraco tree to locate the node we want. In reality most of the time these sorts of links are closer to the curent node in the tree then to the root node but the root node is all that is shown and we must navigate dow to the item we want.

Thus This pull request: https://github.com/umbraco/Umbraco-CMS/pull/121

This change is a huge time save for any editor with more then one or two levels of hierarch in his site. What is does is quite simple. Normal when using the Copy, Mode, or any Content Picker properties on a document the popup tree selector starts at the root of the site and asks the user to browser for the node they want. In this patch the current content page being edited is pre-located and the tree expanded to show it. This adds a very short delay before the user can use the tree picker but now if there are 3-4 levels of hierarchy the relevant section will already be located and selecting nodes adjacent or related to the current node is significantly faster. Also the full tree is still there so it take no extra time if you want something completely different or unrelated to the current node. (This does not affect media pickers because there is no correlation there to the current document)


Funka! 05 Sep 2013, 23:35:56

Wow, wonderful! I tried adding this functionality to Umbraco myself almost a year ago and could never figure out how to get the tree to expand to my desired node!

Since then, I've also thought to myself: how nice would it be if the content/media picker would remember the last node you moved something to or picked something from, and show that expanded as well... This could be accomplished by setting a session var upon successfully picking something. Or, just have the picker tree expansion-state be the exact same from instance to instance.

For example, if I need to move 5 pages into a different section of my website, every time I choose "Move", I'd like the Move-Dialog to remember and open up the last place I moved something to. (Not necessarily also where I'm moving something ''from'', although sometimes it is nearby and great to have too.)

I agree with exactly what you mentioned, that often times you're doing the same type of thing over and over, and/or picking related things from the same or neighboring section. Note, this "sticky" picker memory would be per each tree picker, not globally! For example, my "Move dialog" would remember the last place I moved something to ''separately'' from where I maybe copied something, which is separate from maybe a picker on a document type.

Harry Kakoulidis 04 Apr 2014, 10:11:44

This should definitely be implemented. Too much time is wasted selecting the folder each time. I hope this gets into version 7 also.

Priority: Normal

Type: Feature (request)

State: Fixed


Difficulty: Normal

Category: UI

Backwards Compatible: True

Fix Submitted: Pull request

Affected versions: 6.1.4

Due in version: 6.2.0


Story Points: