Last modified: 2010-12-29 02:04:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T27556, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25556 - upload a new version warnings due to mwEmbed
upload a new version warnings due to mwEmbed
Status: RESOLVED FIXED
Product: mwEmbed
Classification: Unclassified
Add media wizard (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Michael Dale
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-10-17 21:50 UTC by Derk-Jan Hartman
Modified: 2010-12-29 02:04 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Derk-Jan Hartman 2010-10-17 21:50:23 UTC
When I upload a new version, with the mwEmbed gadget enabled, I always get a warning, because the file currently exists. There is no feedback on why this error is occurring, but it is because you are overwriting the earlier file of course.

This is a question of functionality that is reduced by the usage of this gadget, because normally, you do get such visual feedback and explanation. I looked into it, and found that the submit actually triggers an API call with jsonfm, apparently on purpose, so providing such visual feedback is not possible atm.

It seems that the action of the form is remapped to an API destination. instead of using an XHR command and that jsonfm is used to prevent IE from downloading the response. This is probably not a good idea for Commons "upload new version" uploads to Commons.
Comment 1 Michael Dale 2010-12-29 02:04:25 UTC
I just tested this with r79151 and the upload interface with XHR request is triggered.

You do have to select the ignore warning checkbox to avoid the file override warning. But I think that warning is ok.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links