Django

Code

Ticket #5547 (closed: fixed)

Opened 1 year ago

Last modified 6 months ago

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

Reported by: brosner Assigned to: nobody
Milestone: Component: Admin interface
Version: newforms-admin Keywords: nfa-blocker
Cc: Triage Stage: Ready for checkin
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

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

5547_datetimefield_default_fix.diff (0.8 kB) - added by brosner on 09/19/07 19:08:00.

Change History

09/19/07 19:08:00 changed by brosner

  • attachment 5547_datetimefield_default_fix.diff added.

09/20/07 03:30:55 changed by Simon G. <dev@simon.net.nz>

  • needs_better_patch changed.
  • stage changed from Unreviewed to Ready for checkin.
  • needs_tests changed.
  • needs_docs changed.

12/10/07 10:54:20 changed by brosner

  • keywords set to nfa-blocker.

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

02/29/08 00:25:05 changed by brosner

  • status changed from new to closed.
  • resolution set to fixed.

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

Add/Change #5547 ([newforms-admin] DateTimeField won't honor default value)




Change Properties
Action