> > or must we implement this ? it sounds like you were trying to > implement this. >
I was explicitly calling save_FOO_field in my view before calling save() on the model, if that's what you mean. On Jun 18, 10:37 pm, felix <[EMAIL PROTECTED]> wrote: > sorry, I can't quite help you. > > I'm not able to get ImageField to work at all. > > you say save_FOO_field(filename, raw_contents) > > it looks like the this method is magically added to the model, right ? > > or must we implement this ? it sounds like you were trying to > implement this. > > did you ever get it ? > > I also find it very suspicious that since nothing is being succesfully > uploaded, django is still adding more and more _ to the file name. > the MEDIA_ROOT is correct, the subfolder is already there and has > correct permissions, but no files are making it there. > > On Jun 8, 8:08 am, chefsmart <[EMAIL PROTECTED]> wrote: > > > Hi, can someone help me with the following please: - > > > I have a newform with animagefield. The upload is working fine [using > > save_FOO_file(filename, raw_contents)], but I'm not sure what value to > > assign to the model'simagefield, or how to assign it. > > > The django documentation for save_FOO_file says <begin_quote> If a > > file with the given filename already exists, Django adds an underscore > > to the end of the filename (but before the extension) until the > > filename is available. <end_quote> > > > How do I know what filename the uploaded file eventually get? How do I > > assign this to the model'simagefieldbefore calling save() on the > > model? > > > Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
