I can't reproduce this in a simple setup, maybe first of all try to update the version number in ~/Config/ClientDependency.config (just make it 1 higher or lower) and thoroughly refresh your browser cache.

Do you have this issue on your local environment or after pushing the upgrade to the server? Maybe some files didn't get updated?

Hi Sebastiaan,

Already did the clientdependency thing and also removed all client cache, but still the same problem.

Did a nuget update from 7.8 to 7.12 and testing it on a local machine.

Also tried removing entire bin, umbraco and umbraco_client and restore nuget packages, so I didn't have any old umbraco files, but still same problem..

I've also had the same issue. Out of interest, are you using it within Nest Content Remko?

Mine was an upgrade from 7.11.1 to 7.12

No, not with nested content, just regular mntp.

Steps to reproduce:

1. Install Umbraco 7.12.0 (via NuGet) with default options (including the Starter Kit)
2. Add new MNTP data type (I called mine Generic MNTP, but it shouldn't matter)
   • Set start node to the About us node
3. Add data type to the Home content type (in my example I added a new tab called Testing and called the property Testing as well - I'm good with names like that)
4. Go to the Home node in the content section, and then go to the newly added property
5. When opening up the picker, it starts a tthe root of the content tree, and not the About node as selected.

This is an issue in 7.12.0, but not in 7.11.0 following the same approach as described above.

Maybe this has anything to do with it? "U4-3921 Move/Copy/Content-Picker time saver - pre-selects current node " http://issues.umbraco.org/issue/U4-3921

While I of course wished we never shipped with bugs, reading this thread made my day - thank you to everyone who contributes and participates in making Umbraco better. From bug reporting, to investigating ways to reproduce, to confirming, to pointing to potential root causes.

Massive High Five You Rock, everyone. This is what Umbraco is.

/n

As a potential solution can you test the following:

In ~/Umbraco/Js/umbraco.controllers.js find function treeLoadedHandler and replace it with:

    function treeLoadedHandler(ev, args) {
        //args.tree contains children (args.tree.root.children)
        $scope.hasItems = args.tree.root.children.length > 0;
        tree = args.tree;
        var nodeHasPath = typeof node !== 'undefined' && typeof node.path !== 'undefined';
        var startNodeNotDefined = typeof dialogOptions.startNodeId === 'undefined' || dialogOptions.startNodeId === '' || dialogOptions.startNodeId === '-1';
        if (startNodeNotDefined && nodeHasPath) {
            $scope.dialogTreeEventHandler.syncTree({
                path: node.path,
                activate: false
            });
        }
    }

the last curly here is right before the line that says //wires up selection

Then update the version number in ~/Config/ClientDependency.config (just make it 1 higher or lower) and thoroughly refresh your browser cache.

The problem seems to be that we didn't take into account whether or not a startNodeId was specified when opening the tree at the current location.

Look forward to hearing if this helps!

still seems to cause the issue of not taking the user to the correct node.

Okidoki but as I recall you had the problem from withing nested content, right? I haven't tested that and I don't know if that problem was already present in earlier versions?

If it's not in NC, then do you have steps to repro? How to configure MNTP, how does your content tree look, what did you see, what did you expect? :)

Just to chime in, the suggested fix solves the problem for my solution ;)

Thanks Owain! Always good to report when something is not working, would like to be as confident as possible that something is fixed.

I tried your example and it seems to work for me:

Can you open your dev tools > Sources > Umbraco > Js > umbraco.controllers.js and make sure that the code has actually been updated in your browser? Sometimes caches are extremely persistent.

For me it worked, thanks all!

Make sure you replace the right function, because function treeLoadedHandler appears more than once in umbraco.controllers...

So as in screenshot, replace function on line 4324.

Hi, I checked my code location and you are correct Remko, I pasted it in the wrong place. It's now working :)

O.

Have the same issue in 7.13.2 :(

is working on a reply...