I run LeBlender on an Umbraco version 7.6.1 installation, and haven't noticed anything wrong, including Carousel. On the other hand, I've had trouble with TinyMCE, where I can't post links anymore, but suppose this is another case.

Tomorrow, a new version 7.6.2 is scheduled to be tested (if published as planned).

Just to chime in...

I am running LeBlender on 7.6.1 assembly: 1.0.6337.40631 and it works perfectly.

However, I did have to compile the .dll myself to use a more recent version of the JSON library as per the related issue.

Just clone the LeBlender repo, update the various dependencies and compile...

OK ... So I have more information as to why this may not be functioning properly.

When I create the datatype (grid editor) for the Carousel I can save it but when I try to go to another area of the back office I get this error, "Unsaved Changes":

When I clicked on it the dialogue options for the carousel grid editor CHANGED and included these two paths to LeBlendereditor.html and Base.cshtml ... AND ... a block of "optional" configuration that was already populated with this code:

{
    "editors": [
        {
            "name": "Image",
            "alias": "image",
            "propretyType": {},
            "dataType": "135d60e0-64d9-49ed-ab08-893c9ba44ae5"
        },
        {
            "name": "Title",
            "alias": "title",
            "propretyType": {},
            "dataType": "0cc0eba1-9960-42c9-bf9b-60e150b429ae"
        },
        {
            "name": "Summary",
            "alias": "summary",
            "propretyType": {},
            "dataType": "c6bac0dd-4ab9-45b1-8e30-e4b619ee5da3"
        }
    ],
    "min": 1,
    "max": 5,
    "frontView": "",
    "renderInGrid": "1"
}

I get stuck in the "unsaved changes" loop here ... the only way to exit this section is to click "discard changes".

Anyone have any ideas as to what's happening ...?

I can't check my site at the moment, but have you try to write the path to where the carousel example is installed in the Render textbox?

Have you tried this with the ~ (tilde) sign first (not sure if it's necessary)?

I think I remember that I couldn't get LeBlender to work without path in Render-textbox, and wondered why this textbox was optional. I got all my LeBlender editor in the same directory, and I have a path in each of these Render textbox (only my own editors, include the supplied examples), and all of them work fine.

When I change the property for Image from Data Type (obsolete) Media Picker (Property editor alias: Umbraco.MediaPicker), to the new Media Picker (Property editor alias: Umbraco.MediaPicker2), I've got the same message.

_

Frontend :

"Object reference not set to an instance of an object."

_

In backoffice:

"Something went wrong with this editor, below is the exception detail:

Object reference not set to an instance of an object."

So, are you using Umbraco.MediaPicker (the obsolete that work with LeBlender), or the new Umbraco.MediaPicker2 ?

https://our.umbraco.org/Documentation/Getting-Started/Setup/Upgrading/760-breaking-changes

Umbraco 7.6 Breaking Changes

Property Editors storing UDI instead of ID (U4-9310)

The property editors for pickers for content, media, members and related links have been updated to store UDI instead of node ID. Pickers in sites being upgraded have been marked as obsolete, but will continue to work as they always did. New sites will have the obsolete pickers filtered out from the list of available property editors, but they can be enabled by a configuration flag.

Look at some of the content in parameterconfig.prevalues.controller.js

/***************************************/
/* legacy adaptor 0.9.15 */
/***************************************/

if ($scope.dialogData.parameter && $scope.dialogData.parameter.propretyType) {

    switch ($scope.dialogData.parameter.propretyType.name) {
        case "Textstring": $scope.dialogData.parameter.dataType = "0cc0eba1-9960-42c9-bf9b-60e150b429ae";
            $scope.dialogData.parameter.propretyType = {};
            break;
        case "Textarea": $scope.model.value.dataType = "c6bac0dd-4ab9-45b1-8e30-e4b619ee5da3";
            $scope.dialogData.parameter.propretyType = {};
            break;
        case "Rich Text Editor": $scope.dialogData.parameter.dataType = "ca90c950-0aff-4e72-b976-a30b1ac57dad";
            $scope.dialogData.parameter.propretyType = {};
            break;
        case "Boolean": $scope.dialogData.parameter.dataType = "92897bc6-a5f3-4ffe-ae27-f2e7e33dda49";
            $scope.dialogData.parameter.propretyType = {};
            break;
        case "Media Picker": $scope.dialogData.parameter.dataType = "93929b9a-93a2-4e2a-b239-d99334440a59";
            $scope.dialogData.parameter.propretyType = {};
            break;
        case "Multi Media Picker": $scope.dialogData.parameter.dataType = "7e3962cc-ce20-4ffc-b661-5897a894ba7e";
            $scope.dialogData.parameter.propretyType = {};
            break;
        case "Content Picker": $scope.dialogData.parameter.dataType = "a6857c73-d6e9-480c-b6e6-f15f6ad11125";
            $scope.dialogData.parameter.propretyType = {};
            break;
        case "Multi Content Picker":
            $scope.dialogData.parameter.dataType = "";
            break;
    }

}

Not sure what this does, but could it be that if we will use the new Media Picker, that LeBlender must be upgraded with a new version?

SUCCESS ....!!!!! The old media picker (obsolete) is available AND works!

I can render the carousel sample in the browser AND in the back office now.

TOM ... you're a genius ... thanks to you I have LeBlender up and running. Now I just need to go back and only enable that specific property type (and not the whole bunch of deprecated property types).

Can't thank you enough for your help Tom.

In summary, I've just installed Umbraco version 7.6.4, and LeBlender ver 1.0.8.4 package via Umbraco backoffice and had to put these two settings in umbracoSettings.config under <content>:

<ShowDeprecatedPropertyEditors>true</showDeprecatedPropertyEditors>
<EnablePropertyValueConverters>false</EnablePropertyValueConverters>

Then I had to add a new Data Type and select (Obsolete) Media Picker, and use this data type when setting up LeBlender editors. You can't select the new Media Picker (Umbraco.MediaPicker2) because it is another type of pickers (UDI picker), and will not work with the accompanying examples provided with the LeBlender installation.

I have been getting the same error. Then I switched to the obsolete media picker and have a new error: "String "1098" is not a valid udi."

var imageUrl = String.IsNullOrEmpty(highlight.GetValue

I'm on version 7.6.4 and using Umbraco Cloud.

Any help would be much appreciated since I am running circles around upgrade incompatibilities.

Thanks!

is working on a reply...