Last modified: 2011-09-07 19:48:51 UTC
When saving the description on Step 3 to proceed to step 4, the upload wizard is stuck on Step 3 with the spinner spinning. It may be a browser compatibility issue, I've asked people experiencing this issue to provide additional information.
Will reconsider this bug to be about any and all API errors that can block progress on the description page.
One reason this happens: 'badtoken' errors -- if session times out in between uploading and describing. Solution -- wrap the final metadata POST in a "postWithApiEditToken" call as we do with initial upload. This will retry the post with a fresh token if it encounters a badtoken error.
(In reply to comment #2) Except... we're already doing that? The badtoken error *should* be impossible... unfortunately so far can't replicate > One reason this happens: > > 'badtoken' errors -- if session times out in between uploading and describing. > > Solution -- wrap the final metadata POST in a "postWithApiEditToken" call as we > do with initial upload. This will retry the post with a fresh token if it > encounters a badtoken error.
Other errors that can occur - renameerror: if you accidentally enter a title like "foo.jpg", the system will try to rename it to "foo.jpg.jpg". Strip extensions, or disallow them
*** Bug 26076 has been marked as a duplicate of this bug. ***
blocking on 28577 since it describes the need for blacklist checking (which this bug just alludes to)
This bug breaks down into several parts. If an error occurs on the details page submission, it should work like it did with errors on the upload page submission. 1) - The UI should catch any and all errors. Sort of done, but it doesn't do much with them now 2) - Removing the failed submissions should be possible. Progress made on this with r85694, can now remove an upload from anywhere, especially at a deeds interface. Now needs interface for Description page errors. 3) - Retrying the failed submissions should be possible. 4) - Errors which can be fixed by fixing the title should open up the interface again for that, and allow resubmission. 5) - Errors with the title which can be avoided (such as Blacklist) should be surfaced earlier Probably won't block on this for 1.0, as we have issues with TitleBlacklist that we don't understand now.
Oops, the previous comment for (2) should have linked to r86594
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
re: comment #7, points 1-5 have been implemented and bugs with each feature should be broken out when discovered
