Last modified: 2004-09-19 06:27:51 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 284 - __NOTOC__ in template no longer removes TOC from page using the template
__NOTOC__ in template no longer removes TOC from page using the template
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
: 303 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2004-09-03 03:07 UTC by Timwi
Modified: 2004-09-19 06:27 UTC (History)
1 user (show)

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


Description Timwi 2004-09-03 03:07:03 UTC
Originally submitted by Andre Engels (a_engels)  2004-05-28 18:58

Placing the text __NOTOC__ in a template does not any 
more remove the table of contents in pages using the 
Comment 1 Timwi 2004-09-03 17:05:09 UTC
Personally, I prefer it this way.  You can always insert a __NOTOC__ into the
page where the TOC is not supposed to appear.  Having a __NOTOC__ in a template
influence all the pages that use the template would be annoying because, should
you ever want a TOC in a page using the template, you would have to counteract
the effect by inserting a __TOC__ at the right place.
Comment 2 Timwi 2004-09-03 19:40:09 UTC
*** Bug 303 has been marked as a duplicate of this bug. ***
Comment 3 JeLuF 2004-09-19 06:27:51 UTC
fixed in HEAD and REL1_3. See Bug 60

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