DateTimeFields with auto_now_add = True in admin

[philippe.normand@…]

Expose a DateTimeField with auto_now_add = True to the admin, try to add a new object. You can see the date field with empty values (no calendar, etc). Save the object, you'll get a validation error.

Example model:

class Article(meta.Model):
    fields = (
        meta.CharField('title', 'title', maxlength=200, core=True),
        meta.TextField('data','data'),
        meta.DateTimeField('date','date',auto_now_add=True),
    )

    admin = meta.Admin(
        fields = (
            (None, {'fields': ('title', 'date','data',)}),
        ),
    )

If i un-expose the 'date' field from admin, everything works fine.

[Adrian Holovaty]

We worked this out via IRC.

[jbennett@…]

Would it be possible to get the resolution of this issue, or at least a helpful summary, posted here in the ticket? The IRC log site is unreachable at the moment, so there's currently no way to find out how this was solved.

[jbennett@…]

I finally was able to pull up the IRC log; the solution, apparently, was to use 'default=meta.LazyDate()' instead of 'auto_now_add=True'. In which case, shouldn't the model documentation reflect this, at least until auto_now_add works as advertised?

[aCC]

@jbennett

Thanks a lot for digging this up! Finally it works like it should.

[oliver.andrich@…]

I can understand the logic behind making the fields not editable when auto_now_add and auto_now are used, but then it shouldn't also be possible to use the fields inside the fields parameter inside a meta.Admin() call.

Or even better, I would highly appreciate to get them displayed read only. I don't want to change them, but I want to look at them. The admin interface is/should be a management console and not just an "item creation" workbench. At least this is what I understood.