Re: Wierd FileField behavior
Had a look at diff from 9765 and 9766. I think thata changes in release 9766 in db/models/fields/files.py somewhow broke admin site. 9766 address ticket #10044 allowing direct assignment of File object. It extends FileField model capability so I think we should focus to solve the issue on admin site instead of rolling back to 9765. Maybe a custom FileField to be used in admin? Pierpaolo On 12 Feb, 17:01, numshubwrote: > > I tried both 9765 and 9766. > > Indeed, in 9765 I don't come accross the problems mentioned. In 9766 I > > do. > > > Files that were changed between these versions (by Jacob): > > db/models/fields/files.py > > core/files/base.py > > > Erwin > > I have the same problem too. > 9765 works fine. 9766 doesn't. > I'm going to have a look at the above files to find out. > > Pierpaolo --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Wierd FileField behavior
> I tried both 9765 and 9766. > Indeed, in 9765 I don't come accross the problems mentioned. In 9766 I > do. > > Files that were changed between these versions (by Jacob): > db/models/fields/files.py > core/files/base.py > > Erwin I have the same problem too. 9765 works fine. 9766 doesn't. I'm going to have a look at the above files to find out. Pierpaolo --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Wierd FileField behavior
> Revision 9766 introduced some changes related to file fields, can > you try to refine your tests and see if it is the one that broke > things in your case and report back please? I tried both 9765 and 9766. Indeed, in 9765 I don't come accross the problems mentioned. In 9766 I do. Files that were changed between these versions (by Jacob): db/models/fields/files.py core/files/base.py I can't dig into this any deeper atm, but hope I've pinpointed the problem somewhat... Erwin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Wierd FileField behavior
Cool, you saved my life On Feb 3, 10:50 pm, Ramiro Moraleswrote: > On Tue, Feb 3, 2009 at 9:40 AM, Erwin Elling wrote: > > >> I went back to 9781 (which was still on my system for a previous > >> project) and the problem seems not to exist here. Haven't had the time > >> to dig into this any further, but maybe this helps someone else. > > > Sorry, made a mistake; On 9781 the problem is still there. > > On 9084 (also quite randomly chosen) it seems to be allright. > > Revision 9766 introduced some changes related to file fields, can > you try to refine your tests and see if it is the one that broke > things in your case and report back please? > > -- > Ramiro Morales --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Wierd FileField behavior
On Tue, Feb 3, 2009 at 9:40 AM, Erwin Ellingwrote: > >> I went back to 9781 (which was still on my system for a previous >> project) and the problem seems not to exist here. Haven't had the time >> to dig into this any further, but maybe this helps someone else. > > Sorry, made a mistake; On 9781 the problem is still there. > On 9084 (also quite randomly chosen) it seems to be allright. Revision 9766 introduced some changes related to file fields, can you try to refine your tests and see if it is the one that broke things in your case and report back please? -- Ramiro Morales --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Wierd FileField behavior
> I went back to 9781 (which was still on my system for a previous > project) and the problem seems not to exist here. Haven't had the time > to dig into this any further, but maybe this helps someone else. Sorry, made a mistake; On 9781 the problem is still there. On 9084 (also quite randomly chosen) it seems to be allright. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Wierd FileField behavior
On Feb 3, 12:10 pm, Erwin Ellingwrote: > It's probably not DrKayBee's view that's causing problems. Seems like > it's the adminviews. This was on the latest svn revision (9807). I went back to 9781 (which was still on my system for a previous project) and the problem seems not to exist here. Haven't had the time to dig into this any further, but maybe this helps someone else. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Wierd FileField behavior
Show us the code for your view. But are you sending through the files in the POST each time? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Wierd FileField behavior
Hi, I have a simple profile model which includes the option to upload a File (FileField) and a photograph (ImageField). These two fields show somewhat undesirable behavior: (1) Let's say I create a profile and upload a photo through the admin. (2) My member view page shows my photo and other profile details. (3) Then let's say I go back to change something in my address field. The filefield correctly shows the "current file" which I uploaded in (1). I make no other changes and hit Save (4) I reload my member view page. Now the link to my photograph is broken.. (photo doesn't exist) (5) I go back into admin and find there's no photograph associated with my profile. Why does it do this? Is there no way to fix this? Am I doing something wrong? Do I need to upload a file to the database and have it only store a FilePathField? Is there a workaround? 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---