Yes, I believe that this is "intentional", you can save it, but you can't publish if the validation fails. It is so you can come back to it to fix issues.
Except I don't think you are. You are doing a "Save and Publish", which only does the publish part if the validation passes.
It does the "Save", validates the page data, and then fails so doesn't publish showing you the red error notification about validation.
Are you seeing the missing field no longer showing on the front end? Because that would indicate if the publish is still triggering. Does that make sense?
Required fields area saved regardless of validation
Do others experience that required fields are saved regardless of validation ? In my case it happens in Block List ?
Video: https://jottacloud.com/s/0501e62f594be004bfda8ef732764b9338d
Yes, I believe that this is "intentional", you can save it, but you can't publish if the validation fails. It is so you can come back to it to fix issues.
I could well be wrong though.
Nik
But I am publishing, hence the big green button :)
Except I don't think you are. You are doing a "Save and Publish", which only does the publish part if the validation passes.
It does the "Save", validates the page data, and then fails so doesn't publish showing you the red error notification about validation.
Are you seeing the missing field no longer showing on the front end? Because that would indicate if the publish is still triggering. Does that make sense?
Thanks
Nik
Ahhh ... you're absolutely right.
That's gonna require all my diplomatic skills to explain that to the client :)
Hi again Nik,
The bonus question is then, why is there a difference on how the fields validate ?
In this example I'm using a Umbraco.MultiUrlPicker, which actually prevents the page from saving before it's tries to publish.
Link to video: https://jottacloud.com/s/050cfd38f3fe2cb4ef988613c7b9f6c56f7
That to me would be a bug in the CMS, something about how that property renders when in an overlay or something is validated at a different point.
I would raise it on GitHub :-)
is working on a reply...