Last modified: 2014-06-09 06:18:01 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 T40534, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38534 - Add LiquidThreads status to MediaWiki's info action
Add LiquidThreads status to MediaWiki's info action
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Alex Monk
: easy
Depends on: 38559
Blocks: 38450
  Show dependency treegraph
 
Reported: 2012-07-20 18:23 UTC by MZMcBride
Modified: 2014-06-09 06:18 UTC (History)
5 users (show)

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


Attachments

Description MZMcBride 2012-07-20 18:23:21 UTC
Whether a page is using LiquidThreads should be indicated in the output of MediaWiki's info action. This can be done through global variables or via the use of the {{#UseLiquidThreads:1}} magic word (or something similar).
Comment 1 Sam Reed (reedy) 2012-07-20 19:55:38 UTC
(In reply to comment #0)
> Whether a page is using LiquidThreads should be indicated in the output of
> MediaWiki's info action. This can be done through global variables or via the
> use of the {{#UseLiquidThreads:1}} magic word (or something similar).

Some form of a Hook should be added to core, allowing extensions to add extra output to this page
Comment 2 Alex Monk 2012-10-06 21:06:17 UTC
Gerrit change #26970
Comment 3 MZMcBride 2012-10-06 21:29:23 UTC
(In reply to comment #2)
> Gerrit change #26970

Thanks for working on this. It probably makes sense to add this info to an existing section (such as "Basic information") rather than adding a separate section. I worry adding sections per-extension will lead to a situation similar to what we have right now with Special:Preferences. As discussed on IRC, I guess it'd be something like this:

$pageInfo['header-basic'][] = array( wfMessage( 'Moo' ), wfMessage( 'True' ) );

In response to Siebrand, given that {{#UseLiquidThreads:}} or whatever can change a page's status, I'm not sure being quiet about a page not using LQT if it can in theory is a good thing.

I'm also not sure if I see where you define the messages used in your Gerrit change (e.g., "pageinfo-usinglqt-yes"). <https://gerrit.wikimedia.org/r/#/c/26970/1/i18n/Lqt.i18n.php,unified> is really confusing me, but that may be me or Gerrit being stupid.
Comment 4 Alex Monk 2012-10-07 14:19:05 UTC
The same applies to bug 40829 (Gerrit change #27091). CCing Siebrand.

If we're not going to show when a true/false value is false, then maybe we should structure this differently.
Have a list of things which are considered on/true maybe?
Comment 5 Madman 2012-10-07 17:38:43 UTC
Gerrit change #27019 (just leaving this here because I couldn't understand why I was getting a 404 the first three or four times, herp derp).

Upon reflection, I believe I agree with Siebrand; hasn't one of our goals so far been to only show relevant information, hence the change to the restrictions table? It's open to discussion as we don't have any sort of design goal, I suppose, but I don't think any structural change is required. Also, I think if an extension is going to be adding less than two rows to action=info, it should do so in one of the tables core provides.
Comment 6 Siebrand Mazeland 2012-10-07 19:50:28 UTC
You may want to ask for input from design@lists, as ui/ux is important here.
Comment 7 Alex Monk 2012-10-07 22:55:33 UTC
I've thought about this for a bit and decided to simply only output when it's true/yes/on.
Comment 8 Nemo 2013-01-11 18:51:08 UTC
-easy: being LQT.
Comment 9 MZMcBride 2013-01-12 05:12:41 UTC
(In reply to comment #8)
> -easy: being LQT.

This is idiotic. Restoring the easy keyword.
Comment 10 James Forrester 2013-02-11 19:33:35 UTC
This has now been merged - see Gerrit change #26970. Closing.

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


Navigation
Links