Last modified: 2006-01-15 04:14:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 3263 - "Reason" field not carried over for delete-and-move
"Reason" field not carried over for delete-and-move
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Low trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch, patch-need-review
Depends on:
  Show dependency treegraph
Reported: 2005-08-25 14:17 UTC by James F.
Modified: 2006-01-15 04:14 UTC (History)
0 users

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

Patch to fix the bug (698 bytes, patch)
2005-09-24 20:58 UTC, David Benbennick

Description James F. 2005-08-25 14:17:59 UTC
If trying to move a page, and a reason is entered in the box provided, when
clicking "move" and being told that a delete-and-move can be tried instead, the
reason field should have the text entered when trying to move the page
originally; instead, it isn't, and the reason field is now blank. Push it into
the POST string?
Comment 1 David Benbennick 2005-09-24 20:58:45 UTC
Created attachment 913 [details]
Patch to fix the bug

The problem is simply that the HTML code is

<textarea ... value="the reason" />

when it should be

<textarea ...>the reason</textarea>

This second style is how the "show preview" feature is implemented.
Comment 2 Rob Church 2006-01-15 04:14:51 UTC
Seems to have been corrected in CVS HEAD as it is.

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