I have a nested content property with a dropdownlist in it which contains the type.
I want to show the type in the summary of the nested content, I use {{type}} for it. The result is that the ID of the type is shown.
I read about the angular filter 'ncNodeName', but when I use this I get the follwing error:
Request error: The URL returned a 404 (not found):
/umbraco/backoffice/UmbracoApi/Entity/GetById
When I write my own angular filter, I get the same error.
strange, its completely the same version and assembly.
The only thing that's different is that I did a upgrade from 7.5.x to 7.9.2 last week. In my previous version I added manually the filter using a package.manifest, now in current versions this is build in into the core.
I could test this by removing this package and see what the result is.
It works when I use a contentpicker.
The difference with the dropdown is that the values of a dropdown are not really nodes, they are stored in "cmsDataTypePreValues". So I guess that the can not be resolved with ncNodeName.
ncNodeName filter doesn't work with Multinode picker either.
I should probaly write my own angular filter...
Built in angular filter "ncNodeName" -> Request error: 404 (not found)
Hello,
I have a nested content property with a dropdownlist in it which contains the type.
I want to show the type in the summary of the nested content, I use {{type}} for it. The result is that the ID of the type is shown.
I read about the angular filter 'ncNodeName', but when I use this I get the follwing error:
Request error: The URL returned a 404 (not found): /umbraco/backoffice/UmbracoApi/Entity/GetById
When I write my own angular filter, I get the same error.
Any ideas about this?
Hi Olivier,
how did you setup your Name Template in your NC DataType? Something like this:
I am on version 7.9.2 and works fine.
/Michaël
Hi Michaël,
Yes, I did it like you. (Umbraco version 7.9.2 assembly: 1.0.6634.25789)
Olivier,
strange, its completely the same version and assembly.
The only thing that's different is that I did a upgrade from 7.5.x to 7.9.2 last week. In my previous version I added manually the filter using a package.manifest, now in current versions this is build in into the core.
I could test this by removing this package and see what the result is.
Keep you posted!
( See you at BUUG tonight? )
/Michaël
Michaël,
It works when I use a contentpicker.
The difference with the dropdown is that the values of a dropdown are not really nodes, they are stored in "cmsDataTypePreValues". So I guess that the can not be resolved with ncNodeName.
ncNodeName filter doesn't work with Multinode picker either. I should probaly write my own angular filter...
(I will be at BUUG tonight)
Olivier
is working on a reply...