Last modified: 2012-12-16 08:34:11 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 T45168, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43168 - Gadget HotCats doesn't behave with Index: forms
Gadget HotCats doesn't behave with Index: forms
Product: MediaWiki extensions
Classification: Unclassified
ProofreadPage (Other open bugs)
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: Wikisource
  Show dependency treegraph
Reported: 2012-12-16 02:18 UTC by billinghurst
Modified: 2012-12-16 08:34 UTC (History)
3 users (show)

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


Description billinghurst 2012-12-16 02:18:09 UTC
The somewhat universal gadget HotCat doesn't interface well with the Index: page forms, in fact it basically strips it of data and applies a blank template

The form has never worked well with HotCat even back to ThomasV's efforts, but it would be useful if there was a designated interactive zone where HotCat could work.  This is predominantly for maintenance work.

At this point of time, enWS will probably have to consider neutering HotCat in that namespace.
Comment 1 Tpt 2012-12-16 08:11:28 UTC
I think that, if we want to make HotCat work with index pages, we will need to customize it to work with the index pages edit form. I don't want to include bad hack to ProofreadPage only to make it work with HotCat.
Comment 2 billinghurst 2012-12-16 08:30:22 UTC
Okay, are you suggesting that becomes a WONTFIX here, and something that is taken back to the WS wiki(s)?  It is sometimes hard to know where the Extension starts and stops with relation to Index: pages. :-)
Comment 3 Tpt 2012-12-16 08:34:11 UTC
Yes, it's what I suggest: I believe that the extension mustn't have any code relying on a gadget. But if there are issues with the current edit system of the extension, they have to be fixed in the extension.

So I close as WONTFIX.

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