Web Images Videos Maps News Shopping Gmail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Proposed solution to deleting contents of FileField
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Bryan Chow  
View profile  
 More options Aug 9 2006, 10:55 pm
From: "Bryan Chow" <br...@verdjn.com>
Date: Wed, 9 Aug 2006 19:55:12 -0700
Local: Wed, Aug 9 2006 10:55 pm
Subject: Proposed solution to deleting contents of FileField
Hi All,

Ian Clelland and I have been working on a way to address the problem
that Django FileFields and ImageFields can't be cleared once they've
been set. We've posted a proposed solution here [1].

Our solution differs from the one proposed in Ticket #22 [2] in that
it's somewhat simpler, isn't restricted to admin, works within the
existing FormWrapper framework, and is compatible with post-MR code.
It currently subclasses FileField and works as a drop-in replacement,
but we hope that eventually the core FileField code could be changed
to include this functionality.

Ultimately, we'd like to submit this as a patch to Django's FileField,
but would like to get some feedback from the community before we move
further. Comments please :)

Bryan

[1] http://www.verdjn.com/wiki/FileField
[2] http://code.djangoproject.com/ticket/22


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
James Bennett  
View profile  
 More options Aug 9 2006, 11:22 pm
From: "James Bennett" <ubernost...@gmail.com>
Date: Wed, 9 Aug 2006 22:22:09 -0500
Local: Wed, Aug 9 2006 11:22 pm
Subject: Re: Proposed solution to deleting contents of FileField
On 8/9/06, Bryan Chow <br...@verdjn.com> wrote:

> Ian Clelland and I have been working on a way to address the problem
> that Django FileFields and ImageFields can't be cleared once they've
> been set. We've posted a proposed solution here [1].

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.

[1]http://code.google.com/soc/django/appinfo.html?csaid=D7C2A8570706A6F6

--
"May the forces of evil become confused on the way to your house."
  -- George Carlin


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Ian Clelland  
View profile  
 More options Aug 12 2006, 1:48 pm
From: "Ian Clelland" <clell...@gmail.com>
Date: Sat, 12 Aug 2006 10:48:32 -0700
Local: Sat, Aug 12 2006 1:48 pm
Subject: Re: Proposed solution to deleting contents of FileField
On 8/9/06, James Bennett <ubernost...@gmail.com> 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
<clell...@gmail.com>


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google