I've just tried saving the model using the approach followed in Django's unit test and the database gets populated correctly, this reinforces the likelihood of it being an admin-related issue.
Regards, Andrew Ingram, Karen Tracey wrote: > http://code.djangoproject.com/ticket/9545 > > also reports these fields not working, which I found a little > mysterious since the function is tested in the test suite. Your > report provides a clue that the problem may be specifically with the > admin (though the ticket doesn't mention admin), where (without > actually looking at any code) I could guess the path taken to save the > new model with an uploaded image somehow bypasses however these fields > are normally set. You might want to note in that ticket how you are > encountering this problem in the admin. The ticket also notes a > custom save method can be used to get around the problem, which you > may want to try if you want to get things working before the root > cause of the problem is identified and fixed. > > Karen > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
