Last modified: 2014-08-11 17:51:12 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 T71273, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 69273 - Make PageTranslation and PageMigration fields bigger/more usable
Make PageTranslation and PageMigration fields bigger/more usable
Status: PATCH_TO_REVIEW
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
master
All All
: High enhancement (vote)
: ---
Assigned To: Pratik Lahoti
:
Depends on:
Blocks: 65740
  Show dependency tree / graph
 
Reported: 2014-08-07 22:23 UTC by Nemo
Modified: 2014-08-11 17:51 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nemo 2014-08-07 22:23:25 UTC 
The blue button is in the centre of the screen. I would use some more space to type the titles of the pages to act on.
Comment 1 Nemo 2014-08-08 23:27:15 UTC 
Niklas also asks why there are two separate fields for basepagename and language code subpagename: is it really needed?

It would also be useful, for linking purposes, to be able to specify the title in subpage format, like Special:PageMigration/$name. (In case it's easy to do at the same time.)
Comment 2 Pratik Lahoti 2014-08-09 06:39:17 UTC 
Fine, no problem in doing that.
Comment 3 Gerrit Notification Bot 2014-08-09 20:05:54 UTC 
Change 153222 had a related patch set uploaded by BPositive:
Input fields at Special:PagePreparation and Special:PageMigration made bigger and usable

https://gerrit.wikimedia.org/r/153222
Comment 4 Nemo 2014-08-11 17:51:12 UTC 
While the thing in itself is minor, I'm raising priority because figuring out entry points for the feature is something we really must do this week, see bug 65740 comment 1.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links