Different output from Nested Content property on local and server
Hi.
I've setup a Multiple Media Picker in a Nested Content datatype and using it in a Vorto property. Everything is working fine locally, but on the server and on another local machine the output is not the same.
if (product.HasVortoValue("productImages"))
{
var im = product.GetVortoValue<dynamic>("productImages", "en-GB");
var imSource = im[0]["images"].Value;
}
Here is the output on my local machine running VS2013:
Thanks for your reply. Actually Alex Skripnik helped me out and discovered that the issue was solved when Vorto was installed via Nuget. Apparently the dll is different although that sounds weird. And even weirder considering the fact that Vorto was already working perfectly on the local installation when installed directly via the Umbraco backend.
Now everything is running as expected with Vorto handling Nested Content datatypes with the (Single) Media Picker as well as the Multiple Media Picker.
It's very strange, but I checked 2 times, when we are using dll from nuget it works. and we have a problem when we are using dll from Umbraco package. The size of dlls is the same, I don't how it can be.
Different output from Nested Content property on local and server
Hi.
I've setup a Multiple Media Picker in a Nested Content datatype and using it in a Vorto property. Everything is working fine locally, but on the server and on another local machine the output is not the same.
Here is the output on my local machine running VS2013:
And here is the output on a server running IIS - and on another local machine also running VS2013:
All the above are connected to the same SQL database. The Nested Content package has been added via the local Umbraco.
Any help is appreciated.
/Søren
Hi Søren,
This might be more of a question for Matt, (since I don't know that much about Vorto).
From what I can tell about the returning values, the one that returns the
DetachedPublishedContent
would be the correct one.The first value looks like a raw JSON object is returned, which would suggest that Nested Content's PropertyValueConverter isn't being called.
I'm wondering if there are any errors in the /App_Data/Logs/UmbracoTraceLog.txt?
Cheers,
- Lee
Hi Lee,
Thanks for your reply. Actually Alex Skripnik helped me out and discovered that the issue was solved when Vorto was installed via Nuget. Apparently the dll is different although that sounds weird. And even weirder considering the fact that Vorto was already working perfectly on the local installation when installed directly via the Umbraco backend.
Now everything is running as expected with Vorto handling Nested Content datatypes with the (Single) Media Picker as well as the Multiple Media Picker.
/Søren
Weird about the NuGet thing, not sure about that part. Anyway, cool, glad that you've got it sorted.
Cheers,
- Lee
Hi Lee,
It's very strange, but I checked 2 times, when we are using dll from nuget it works. and we have a problem when we are using dll from Umbraco package. The size of dlls is the same, I don't how it can be.
Thanks,
Alex
Hola all,
Problem was that we used
dynamic
. Nested content isIPublishedContent
. The below code works:Thanks Lee for pointing out what was the correct one :)
Jesper
is working on a reply...