-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MNTP returns IPublishedContent #24
Comments
My original code used
It did work for some items, but was sometimes returning null. If I change my code to the following it seems to work.
|
Hi @bjarnef That's really odd (and wrong), I would guess it has something to do what's going on inside GetValue, I'm guessing this method is from LeBlender? Jeavon |
I found it and I'm not sure why it does this and I'm guessing that's what's causing your issues.... |
Hi @Jeavon Yes it is a bit strange, it does seems to work for some of the LeBlender items.
I have also had some issues in some of the (LeBlender) grid editors, when casting an json object to a
but I don't have these issues in projects without property value converter package. The properties |
@bjarnef did you create this issue on LeBlender somewhere? |
@Jeavon I think it is related to this issue Lecoati/LeBlender#80 although not exact same functionally, but an issue how the value is returned from LeBlender when using core property value converters mainly an issue with pickers. |
In the docs it says that MNTP (Multinode Tree Picker) returns
IEnumerable<IPublishedContent>
https://github.com/Jeavon/Umbraco-Core-Property-Value-Converters/blob/v3/Docs/MultiNodeTreePicker.md
However I expirience it returns
IPublishedContent
, but it might be because the datatype instance is limited to select one item?If I used one of the following, it sometimes returned null even a node was picked.
But it is a bit strange, because in some of the items (LeBlender), it works with cast to
IEnumerable<IPublishedContent>
However for a country node, if I instead cast to
IPublishedContent
it does work.We have also ModelsBuilder enabled and use
Our.Umbraco.CoreValueConverters
v3.1.3 on Umbraco v7.5.8The text was updated successfully, but these errors were encountered: