#5619: FileField and ImageField return the wrong path/url before calling
save_FOO_file()
---------------------------------------+------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: leahculver
Status: reopened | Milestone:
Component: Core framework | Version: SVN
Resolution: | Keywords:
Stage: Someday/Maybe | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Changes (by Gulopine):
* keywords: fs-rf-fixed =>
* milestone: 1.0 beta =>
Comment:
Yeah, I'm actually not sure now why I had put `fs-rf-fixed` on this one.
When I add Leah's tests to the #5361 patch, it fails quite reliably, so
it's clearly still an issue. I'll keep it in my head and see what happens
if/when we get that potential future differentiation between db-load and
otherwise. Removing all `fs-rf` tags, as well as the 1.0 beta milestone,
since it clearly won't get taken care of in the immediate future.
The one thing I'd note on this is that the docs probably shouldn't say
"*if* you are using `upload_to`," since it's actually a required argument
on all `FileField`s. That requirement isn't going away after #5361 either,
so it's still important to make it clear.
--
Ticket URL: <http://code.djangoproject.com/ticket/5619#comment:19>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
