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.
Version: unspecified
Severity: normal
OS: other
Platform: Other
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T38680 Upload Wizard release "elvis" (tracking) | |||
| Resolved | None | T29260 UploadWizard 1.0 (tracking) | |||
| Resolved | None | T26758 Upload wizard: API errors that block progress on description page submission | |||
| Resolved | None | T30577 Allow API to test if page title is blacklisted (or is invalid for other reasons) |
neilk wrote:
Will reconsider this bug to be about any and all API errors that can block progress on the description page.
neilk wrote:
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.
neilk wrote:
(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.
neilk wrote:
Other errors that can occur
neilk wrote:
blocking on 28577 since it describes the need for blacklist checking (which this bug just alludes to)
neilk wrote:
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.
Sort of done, but it doesn't do much with them now
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.
Probably won't block on this for 1.0, as we have issues with TitleBlacklist that we don't understand now.
mhershberger wrote:
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
neilk wrote:
re: comment #7, points 1-5 have been implemented and bugs with each feature should be broken out when discovered