Last modified: 2011-04-14 15:13:11 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 12930 - Add categories by default to all errors during parsing
Add categories by default to all errors during parsing
Status: NEW
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Low enhancement with 6 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-05 20:19 UTC by Derk-Jan Hartman
Modified: 2011-04-14 15:13 UTC (History)
3 users (show)

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


Attachments

Description Derk-Jan Hartman 2008-02-05 20:19:15 UTC
I think it would be really handy if there was a Special: page that would list all pages that encountered (pre)parser errors during their last render.
My direct reasoning for these would be references. You often see that a named ref is removed that is still in use by other named refs resulting in:

Cite error: Invalid <ref> tag; no text was provided for refs named yourname

Especially on articles that are not as closely watched, these can persist for quite some time, in part because this error is at the bottom of the page and thus not that visible. We also have similar issues with parserfunctions errors, and even post expansion problems. 

If we had a Special:Errors page that would list all pages that had one of those errors during their last render, then it would be much easier to solve all these issue. One of the reasons is that they often require quite some experience as an editor in order to be solved, but it can take a while before such editors either find the pages themselves, or are pointed at them. With a list, the experienced editors can regularly  check wether their are issues with wikipages that have gone unnoticed and go out and fix them.
Comment 1 René Kijewski 2008-04-06 19:06:43 UTC
Good idea. I would prefer a category. I think it would be easier to implement.
Comment 2 Melancholie 2009-01-28 06:46:02 UTC
Not least after bug 16854 we now have many ugly bold red and technical parser warnings.
A tool for tracking errors is urgently needed.
You can do it by adding a tracking category to messages like
[[MediaWiki:Cite_error_references_no_text]]
[[MediaWiki:Cite_error_refs_without_references]]
[[MediaWiki:Cite error group refs without references]]
etc. etc.

BUT:
That would have to be done for every single message on every single (not seldom rather poorly) informed wiki out there!

So, a special page [[Special:Errors]]/[[Special:ParserErrors]] would be good!
Otherwise add a tracking category by default to all that messages so that it's shown in Betawiki.
Comment 3 Aryeh Gregor (not reading bugmail, please e-mail directly) 2009-01-28 14:18:17 UTC
Categories are the way we should do this.

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


Navigation
Links