Nevermind.. You provided the grain of truth I needed and I think it's
working now.. added required=false to the constructor call.. after
seeing what was in the fields collection with the debugger.
Thanks
On Wednesday, August 5, 2015 at 4:38:36 PM UTC-5, James Bennett wrote:
>
> Have you
I've not and I'm not sure how or where to do that.
On Wednesday, August 5, 2015 at 4:38:36 PM UTC-5, James Bennett wrote:
>
> Have you tried setting "required=False" in your custom field override?
>
> On Wed, Aug 5, 2015 at 3:23 PM, Scott Gibson > wrote:
>
>> The django admin app is requiring a f
Have you tried setting "required=False" in your custom field override?
On Wed, Aug 5, 2015 at 3:23 PM, Scott Gibson wrote:
> The django admin app is requiring a foreign key to be populated even
> though the model is defined and migrated with null=true and blank=true.
>
> What I've found is that
The django admin app is requiring a foreign key to be populated even though
the model is defined and migrated with null=true and blank=true.
What I've found is that the admin app will treat the field as required if
the associated AdminForm(forms.ModelForm) overrides the fields collection
for
4 matches
Mail list logo
