We're looking at using Vorto inside nested content items for some properties. We noticed that mandatory rules are ignored inside the nested content, as also pointed out by Jereon Breuer in his blog post
I understand that it's possible to instead put the whole nested content property inside Vorto, but that's not neccessarily what we want our CMS users to do.
Is there any other work-around for the Mandatory issue, or is there a plan to fix it at any point? Is it a "bug" or a "feature"?
I'm also looking into using Vorto and nested content together (with Vorto wrapping a nested content data type) in Umbraco 7.7. Unfortunately it looks like this issue with mandatory properties is still present. For now we can get around this with extra null checking, but does anyone have any other suggestions for getting around this?
I remember there was an issue with mandatory fields in a nested nested content a while back - could this be related?
Mandatory Vorto properties inside Nested Content
Hi, great plugin.
We're looking at using Vorto inside nested content items for some properties. We noticed that mandatory rules are ignored inside the nested content, as also pointed out by Jereon Breuer in his blog post
I understand that it's possible to instead put the whole nested content property inside Vorto, but that's not neccessarily what we want our CMS users to do.
Is there any other work-around for the Mandatory issue, or is there a plan to fix it at any point? Is it a "bug" or a "feature"?
Hi folks,
I'm also looking into using Vorto and nested content together (with Vorto wrapping a nested content data type) in Umbraco 7.7. Unfortunately it looks like this issue with mandatory properties is still present. For now we can get around this with extra null checking, but does anyone have any other suggestions for getting around this?
I remember there was an issue with mandatory fields in a nested nested content a while back - could this be related?
is working on a reply...