A partial archive of https://discourse-mediawiki.wmflabs.org as of Saturday May 21, 2022.

Are you looking for the issue tracker for a particular extension?

freephile

I know it’s convention to use Project:Support Desk for help with mediawiki, and also convention to use an extension’s talk page as a means to contact the author/maintainer of an extension. I only just realized that there is a dedicated and simple to use interface for searching, reporting and tracking issues per extension. You just have to use the phabricator parameter in the Extension template on your Extension page.

As an extension developer, I find it very difficult to use a Talk page to accomplish meaningful issue tracking and development, so I hope that more emphasis is put on using the Extension Template fully (and that there exists a Phabricator project for every extension!)

If you use the phabricator parameter, this is what you get:

Selection_007

By carefully scrutinizing the differences between my project and other projects like Approved Revs that don’t have a workboard; and looking at the edit history, I came to find out that the “bugzilla” field in Template:Extension could also be used, but is deprecated obviously. Again, the preferred named parameter that addresses this question is ‘phabricator’. That parameter takes the full project name in phabricator as it’s value (in my case “mediawiki-extensions-html2wiki”). When you add that to your extension page, you will automatically get the “Open tasks” and “Report a bug” links that I was looking for. (They’re at the bottom of the infobox; see the image below.) The same parameter also inserts a colored element above the infobox that links directly into the Phabricator workboard for the extension (illustrated above).

Selection_008

A related question: For the Html2Wiki extension, my workboard is at https://phabricator.wikimedia.org/project/board/1094/query/open/ Is there an administrative interface or mechanism where URL-aliases could be mapped so that board 1094 could become Html2Wiki?

Ciencia-Al-Poder

AFAIK there’s no way to make phabricator use the alias Html2Wiki over the 1094 code for that project, when phabricator generates links to the project from phabricator itself. But you can use the alias when linking to it from other places.

Tgr

https://phabricator.wikimedia.org/tag/mediawiki-extensions-html2wiki but it will always link to the landing page of the project (typically the workboard but can be configured), you can’t link specifically to the workboard or the project description page.

If you want to use html2wiki, you can add it as a project alias with the Manage option in the left-hand menu.

freephile

I tried to add a link in the menu for “Report a bug” that goes to https://phabricator.wikimedia.org/maniphest/task/create/?projects=mediawiki-extensions-html2wiki but clicking the menu item only changes the location bar in Chrome and Firefox, but doesn’t actually traverse the link.

I added a couple other custom links in the menu, and it’s the only menu link that doesn’t work.

I can attempt to visit that URL when logged out of gerrit, and it will successfully go to the ‘Create task’ form once I login. But for some reason the menu doesn’t seem to like that link. Thinking it might be unable to handle a querystring, I tested another link with a querystring - it works fine.

I guess I should open a ticket with Phacility

Tgr

Works for me, and I use Chrome.

Tgr

(OTOH I’m pretty sure the report link conflicts with some policy or another :))

freephile

That’s just a test, but I also tried the ‘Report a Bug’ link (twice - I’m sure you noticed), and just tried using it on a Windows machine with Chrome… same result:

  1. Visit Project Workboard for Html2Wiki at https://phabricator.wikimedia.org/project/board/1094/
  2. Click “Report a bug”
  3. Result: address changes in location bar but page remains the same
  4. Place cursor in location bar, press enter
  5. Result: browser navigates to the “Create Task (Simple)” form with the proper project (Mediawiki-extensions-Html2Wiki) pre-filled in the “Tags” form element.
Tgr

Both links work fine for me and they look like completely ordinary links. Maybe you have some browser plugin that’s acting up?

freephile

Weird! Thanks for testing and reporting back that all my problems are just in my head :smile:

Tgr

Tested it on Chrome 64 / Linux, FWIW.