I gave a member 2 properties based on the "ultimate picker" datatype, and checked the mandatory checkbox, now when i create a new member, or edit an existing one, i do get the red validation text that the field is required, but everything else is saved anyway ?
Does anyone else experience this behaviour? this way i have no means to make member properties required.... :(
Yes I think it always was this way. Since a member is only stored in the database the mandatory fields is useless (because it only works with data which can be published). The same thing probably goes for media type fields.
This should of course not be the case (but the validation has been designed for content - not for media/members which inherit thus aren't based on same versioning scheme as Jeroen says).
Making member properties "mandatory" allows blank entries?
I gave a member 2 properties based on the "ultimate picker" datatype, and checked the mandatory checkbox, now when i create a new member, or edit an existing one, i do get the red validation text that the field is required, but everything else is saved anyway ?
Does anyone else experience this behaviour? this way i have no means to make member properties required.... :(
Kind regards,
Rik
Yes I think it always was this way. Since a member is only stored in the database the mandatory fields is useless (because it only works with data which can be published). The same thing probably goes for media type fields.
Jeroen
great news :/
vote up the issue here: http://umbraco.codeplex.com/workitem/29386
This should of course not be the case (but the validation has been designed for content - not for media/members which inherit thus aren't based on same versioning scheme as Jeroen says).
I'll make sure this gets changed for JUNO.
is working on a reply...