Last modified: 2010-05-15 15:41:18 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.
Status: RESOLVED DUPLICATE of bug 7347
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
PC Linux
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-11-27 22:48 UTC by Dan Jacobson
Modified: 2010-05-15 15:41 UTC (History)
0 users

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


Description Dan Jacobson 2006-11-27 22:48:42 UTC
Consider cases like, a page
that mentions its 60 categories in the rendered text. If there were a
__NO_CATEGORY_LIST_AT_END__ capability, the categories wouldn't end up
getting repeated at the bottom.

Categories at the bottom work great for pages like but not
when one wants to give that list structure so puts them in the
rendered body.

You never know what great uses one could come up for a wiki, so a
__NO_CATEGORY_LIST_AT_END__ (or some better name) would be handy.
Or will it lead to bad practices? If so then how to better do my page
for bus route 100 above?
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-11-28 04:00:31 UTC

*** This bug has been marked as a duplicate of 7347 ***

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