Last modified: 2009-01-28 22:28:32 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 T17811, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15811 - "Upload a new version of this file" should refer to a form with different appearance
"Upload a new version of this file" should refer to a form with different app...
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Aaron Schulz
:
: 16980 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-02 18:43 UTC by Ilya Schurov
Modified: 2009-01-28 22:28 UTC (History)
3 users (show)

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


Attachments

Description Ilya Schurov 2008-10-02 18:43:38 UTC
Now the link "Upload a new version of this file" on the image page refer to a page with upload form which is identical to a form of initial upload. This lead to misunderstanding, because behaviour of this form is quite different: the content of "summary" goes only to log, and not updates the description of the image. So some users try to change the description of the image (e.g. add {{Image}} template or fair use rationale) by re-uploading the image with proper "summary" field -- and finally lost their data. It seems to be rather serious problem, because current behaviour of this form is contr-intuitive. The lack of description often leads to deleting of the image, which also have negative effect on attitude of contributors which images are deleted.

This can be solved by changing the form of "secondary" upload. We need at least to have different system messages used in this form to explain user the difference of the behaviour. It will be also good to change "summary" field to text input instead of textarea.
Comment 1 Rémi Kaupp 2008-10-08 20:48:10 UTC
Basically, the following changes would be required on the image replacement form:
* no need to enter a license or categories.
* no need to change the file destination name.
* description should relate to the actual changes being done while replacing the images (such as "crop", "fix white balance", etc.), not the description of the image itself. The interface should mention it.
* the form currently says that we are trying to replace an existing image and we shouldn't do it, but it is exactly what the user wants to do. A different message should be shown.
Thanks.
Comment 2 Mike.lifeguard 2009-01-03 06:06:04 UTC
(In reply to comment #1)
> * description should relate to the actual changes being done while replacing
> the images (such as "crop", "fix white balance", etc.), not the description of
> the image itself. The interface should mention it.

This in particular needs fixing. People just don't understand that the textbox is now an edit summary/log entry - they try to edit the image description page here, which is so so wrong. We should help them.
Comment 3 Aaron Schulz 2009-01-21 15:47:13 UTC
Done in r45963
Comment 4 Rémi Kaupp 2009-01-21 18:06:40 UTC
*** Bug 16980 has been marked as a duplicate of this bug. ***
Comment 5 Ilya Schurov 2009-01-28 16:37:13 UTC
Thank you Aaron! However, I believe, more tweaks are needed: we should have different default text for summary textarea field, wpUploadDescription (e.g. if it is initial download, it have {{Image}} template with needed fields, and if it's updating, such templates looks a little bit confusing).
Comment 6 Aaron Schulz 2009-01-28 19:29:12 UTC
Done in r46465
Comment 7 Lupo 2009-01-28 19:49:04 UTC
Please also see bug 17193, bug 17194, and in particular bug 17200. Thank you.
Comment 8 Aaron Schulz 2009-01-28 19:50:34 UTC
Geeze, new stuff just keeps coming ;)
Comment 9 Aaron Schulz 2009-01-28 22:28:32 UTC
Closing. This bug's issue are resolved.

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


Navigation
Links