Hi Rasmus,

I think it may be to do with the positioning of the Content Type selection modal, (but I haven't tried NC in 7.6.4 yet). As in it's somehow hidden off the screen.

A few other people have raised an issue about this, and we did a potential fix, (unreleased) ...

See here: https://github.com/umco/umbraco-nested-content/commit/9884999e65fbf9be5c2cd43c14f52a4302d1baec

But then a couple of other people had issues with that fix...

See here: https://github.com/umco/umbraco-nested-content/issues/130#issuecomment-306759636

So we're unsure on how to resolve it. I guess it's trying to find a happy medium across all of NC's use-cases, (e.g. standard use + inside a DTGE + inside a Vorto + anything else we've not thought of).

I wish I had more time to investigate and come up with a rock solid solution, alas I currently don't :-( So any help would be hugely appreciated, (not targeting you directly Rasmus, but anyone reading this) :-)

Cheers,
- Lee

Hello Lee

Awesome that you got back so fast ;)

hmm I tested your fix, and for me it worked, only thing i did different was also removing these 3 lines from the JS:

  // Position off screen till we are visible and can calculate offset
        $scope.overlayMenu.style.top = -1000;
        $scope.overlayMenu.style.left = -1000;

And

     var offset = el.offsetRelative("#contentwrapper");

            $scope.overlayMenu.style.top = (Math.round(wrapper.height() / 2) + offset.top) - Math.round(el.height() / 2);
            $scope.overlayMenu.style.left = (Math.round(wrapper.width() / 2) + offset.left) - Math.round(el.width() / 2);

And it works both inside the grid with DTGE and as a standalone datatype without being put into the grid

I dont have vorto but here it seems to be good, with all mentioned use cases!

is working on a reply...