Re: Trouble with (unwanted) field validation

2013-11-11 Thread DJ-Tom
This is really weird - I just tried again and *can't* reproduce it at all ... everything is suddenly working as expected. Thanks anyways ;-) Am Freitag, 8. November 2013 13:41:49 UTC+1 schrieb Sergiy Khohlov: > > answer is simple . Validator would like to check field which is > used for Key.

Re: Trouble with (unwanted) field validation

2013-11-08 Thread Sergiy Khohlov
answer is simple . Validator would like to check field which is used for Key. Look like this field is not set before validation. I would like take a look at model form and part of code before form.is_valid Many thanks, Serge +380 636150445 skype: skhohlov On Fri, Nov 8, 2013 at 2:29 PM

Re: Trouble with (unwanted) field validation

2013-11-08 Thread DJ-Tom
I still didn't get this to work... isn't there anybody that is able to help? Am Mittwoch, 30. Oktober 2013 10:47:34 UTC+1 schrieb DJ-Tom: > > Hi, > > given the following model field: > > room_setup = models.ForeignKey("roomsetup", verbose_name='Default room > setup', blank=True, null=True, defaul

Trouble with (unwanted) field validation

2013-10-30 Thread DJ-Tom
Hi, given the following model field: room_setup = models.ForeignKey("roomsetup", verbose_name='Default room setup', blank=True, null=True, default='') In the modelform __init__ method I'm setting the choices for this field like this: self.fields['room_setup'].choices = roomsetups_as_c