On 8/9/06, James Bennett <[EMAIL PROTECTED]> wrote: > This is certainly a long-standing wart in Django, and on first glance > I like this solution a little better than the patch on #22, but we > also have a Summer of Code student working on major enhancements to > the admin's media support[1]; since there are only a couple weeks left > to go in SoC, I'd advise holding off on comitting any solution until > we see his final results.
Thanks, James -- I hadn't realised that one of the SoC coders was working around FileField and ImageField. The code that we have now was written as a workaround for the problem, rather than as a patch against django source, for just this reason. We don't want to tread on anyone else's work if we can help it -- it just makes for bigger maintenance headaches for us ;) Unfortunately, (for us, possibly,) with further testing, we've discovered a couple of problems with Django's handling of FileFields and ImageFields -- not strictly limited to admin, but in the way that fields tagged "core=True" are handled by manipulators. Because of this, I've created a ticket (#2534) with a patch that fixes the core field handling, and makes FileFields deletable. http://code.djangoproject.com/ticket/2534 Regards, Ian Clelland <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
