-
Notifications
You must be signed in to change notification settings - Fork 63
Issues when using core property value converters #80
Comments
I had switcher from |
Line 49 & 50 in the below file should be removed
Source should never be returned, it should always be Object that is returned |
@soreng could you have a look at this one please? 😁 I think you should be able to reproduce if you add a LeBlender property using Multi Url Picker. E.g. create two datatype instances of Multi Url Picker:
Single Url Picker returns |
hi @bjarnef I can have a look at it later, but I can't really say when it will be :-/ I will be looking into a few thing (maybe a v2) in the not so distant future |
Okay, hopefully you get some time to look at this issue. I have also had some issues when using MNTP for some menu items in a megamenu, where it sometimes returned |
@soreng have you tried LeBlender with ModelsBuilder and property value converters enabled. I have often see then returned value not is they expected inside LeBlender, while it works correct when the properties are directly on document types. It happens for e.g. Multinode Tree Picker, RJP MultiUrlPicker and others. |
@soreng looking forward a fix for this since it has really bothered me now and then, where it was returning different than expected. Hopefully in next release and both a release for Our and NuGet. At the moment I think the latest NuGet version is broken, and doesn't contain some of the fixes which was merged to master branch before the release of the latest NuGet package. |
Maybe a 1.10 is comming out sometime soon - who knows Just need access to upload stuff to the page on our. Will see it I can get that. |
When using core property value converters in Umbraco 7.6.x and 7.7.x and casting e.g. value from an Author Picker
Umbraco.MultiNodeTreePicker2
toIEnumerable<IPublishedContent>
it returns an exception:When I use same logic just in a regular partial view there are no issues.
The text was updated successfully, but these errors were encountered: