Opened 17 years ago

Closed 17 years ago

#5547 closed (fixed)

[newforms-admin] DateTimeField won't honor default value

Reported by: Brian Rosner Owned by: nobody
Component: contrib.admin Version: newforms-admin
Severity: Keywords: nfa-blocker
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

In #899 will fix the newforms bug where the default value from the database field get populated into the form field's initial value. Once that patch gets applied then newforms-admin's formfield_callback still won't honor the default value for DateTimeField's. Here is a patch that will correct that and generally a better clean up anyways.

Attachments (1)

5547_datetimefield_default_fix.diff​ (839 bytes ) - added by Brian Rosner 17 years ago.

Download all attachments as: .zip

Change History (4)

by Brian Rosner, 17 years ago

Attachment: 5547_datetimefield_default_fix.diff​ added

comment:1 by Simon G. <dev@…>, 17 years ago

Triage Stage: Unreviewed → Ready for checkin

comment:2 by Brian Rosner, 17 years ago

Keywords: nfa-blocker added

This is still present in newforms-admin. Tagging with nfa-blocker.

comment:3 by Brian Rosner, 17 years ago

Resolution: → fixed
Status: new → closed

(In [7178]) newforms-admin: Fixed #5547. SplitDateTimeField now honors the default value from the model.

Note: See TracTickets for help on using tickets.
Back to Top