Closed Bug 623431 Opened 14 years ago Closed 14 years ago

Remove ImageUploadFormAsync and VideoUploadFormAsync

Categories

(support.mozilla.org :: Knowledge Base Software, task, P4)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: paulc, Assigned: paulc)

References

Details

(Whiteboard: [qa-])

ImageUploadFormAsync and VideoUploadFormAsync are not necessary. Uploading a draft should be handled as part of the form's clean() method. It might even be possible to get away with a, e.g.: image = image_form.save() and be done with it, leaving the all the upload logic to the model form. While at it, the video validation does not check extensions in VideoUploadForm.clean, but it does so in VideoUploadFormAsync.clean (not an actual problem since the latter must validate first). Since bug 623429 makes handling drafts simpler, I'm adding that as a dependency.
Assignee: nobody → paulc
There's more important stuff on our plate right now and this can wait.
Component: Code Quality → Knowledge Base Software
Target Milestone: 2.4.2 → Future
I'm working on the refactoring and I've already done this part, so => 2.6
Target Milestone: Future → 2.6
Paul, is this done or should it move out?
It's long done on my branch, which fully refactors the gallery frontend as well. I'd rather avoid complications, though, and it's not urgent at all.
Target Milestone: 2.6 → 2.6.1
Priority: -- → P4
Target Milestone: 2.6.1 → 2011Q1
Target Milestone: 2011Q1 → 2011Q2
Blocks: 650407
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: 2011Q2 → 2.8
Closed as [qa-]
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.