Last modified: 2014-06-21 19:58:02 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 T48802, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46802 - Enabling extensions during install process displays empty readonly textbox on status page
Enabling extensions during install process displays empty readonly textbox on...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.21.x
All All
: High normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-02 17:54 UTC by OverlordQ
Modified: 2014-06-21 19:58 UTC (History)
3 users (show)

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


Attachments
Screenshot of the box (70.29 KB, image/png)
2013-04-02 17:54 UTC, OverlordQ
Details

Description OverlordQ 2013-04-02 17:54:41 UTC
Created attachment 12022 [details]
Screenshot of the box

When opting to include extensions during the install process, once it reaches the extension table step the installer displays a empty readonly textbox.

This might be attributable to a specific extension or might be something in the installer itself.

This was tested with 1.21rc1
Comment 1 Waldir 2013-05-04 09:50:43 UTC
From a cursory look at the WebInstallerPage.php code, it seems this isn't specific to any extension, but a feature of the installer itself, called LiveBox (the actual html created is <div id="config-live-log">).

It seems there isn't code to verify whether the box is actually filled to control whether it's shown or not. If this happens live (i.e. after the page is loaded), it could be worth implementing such a function in skins/common/config.js (which already has a function to "Scroll to the bottom of upgrade log").
Comment 2 John Mark Vandenberg 2013-12-07 05:36:08 UTC
Also occurs in 1.22
Comment 3 Mark A. Hershberger 2014-06-21 19:58:02 UTC
Removing target milestone that was in the past.

If you want this in a specific release, have a good reason AND you are willing to find resources to fix this bug, feel free to change it to something appropriate.

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


Navigation
Links