On Oct 28, 9:43 am, John Debs wrote:
> I've written a creaky hack to work around the issue in my own projects
> but after seeing this thread I'm going to take a shot at implementing
> FormSetField (or something like it) myself. If anyone has any code -
> or more arguments for or against that have
vel, a form is a set of fields that gets submitted when
> > > a the form submit button is pressed.
> >
> > > However, this is not the case with model forms and inline formsets
> > > (e.g. an admin page with inlines) -- inline formsets are
> > > disparate from the
a the form submit button is pressed.
>
> > However, this is not the case with model forms and inline formsets
> > (e.g. an admin page with inlines) -- inline formsets are
> > disparate from the model form.
>
> > This creates at least two problems:
> > 1) it'
On Sun, Aug 16, 2009 at 5:45 AM, mrts wrote:
>
> At HTML level, a form is a set of fields that gets submitted when
> a the form submit button is pressed.
>
> However, this is not the case with model forms and inline formsets
> (e.g. an admin page with inlines) -- inline formse
On Sat, Aug 15, 2009 at 8:45 PM, mrts wrote:
>
> At HTML level, a form is a set of fields that gets submitted when
> a the form submit button is pressed.
>
> However, this is not the case with model forms and inline formsets
> (e.g. an admin page with inlines) -- inline formse
At HTML level, a form is a set of fields that gets submitted when
a the form submit button is pressed.
However, this is not the case with model forms and inline formsets
(e.g. an admin page with inlines) -- inline formsets are
disparate from the model form.
This creates at least two problems:
1
Sorry about that, it was better to post to django-users instead. I was
saving the object first using create() manager method, that's why it
was working well.
Maybe I need to attach a function to the post_save signal to move the
file over the custom path with the pk value.
--~--~-~--~~-
but with ModelForms) and the pk value was stored as well, maybe that
thing should work also for inline formsets. I'll try to check it out
better.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django devel
On Mon, May 4, 2009 at 1:26 PM, skam wrote:
>
> I am using inline formsets to save multiple "Photo" models related
> with "Company" model, but "Photo" instance's pk is set to None. I need
> it to set the upload directory and filename
I am using inline formsets to save multiple "Photo" models related
with "Company" model, but "Photo" instance's pk is set to None. I need
it to set the upload directory and filename using the pk value:
Sample model:
def get_photo_image_path(instan
I'll take a look at this, the reason the second part didn't go in
originally(yeah, we thought of it), was that it was considered to be
in a different scope then the rest of the work on unique validation.
On Sep 16, 7:14 am, mrts <[EMAIL PROTECTED]> wrote:
> A bug in 1.0 makes unique_together cons
11 matches
Mail list logo
