Last modified: 2014-11-17 10:34:48 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 T23445, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21445 - Headers not parsed in TOC
Headers not parsed in TOC
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Low major with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://translatewiki.net/wiki/Support
:
: 21691 24683 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-11-09 13:54 UTC by Siebrand Mazeland
Modified: 2014-11-17 10:34 UTC (History)
9 users (show)

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


Attachments

Description Siebrand Mazeland 2009-11-09 13:54:27 UTC
If a Lqt header contains a template that for example parses to "text" and this requires "{{text}}", then the link to the topic will contain {{text}} while the header directly above the topic text read "text".

This is inconsistent behaviour I would like to see fixed. See http://translatewiki.net/wiki/Support for examples.
Comment 1 Andrew Garrett 2010-02-01 03:05:56 UTC
*** Bug 21691 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Garrett 2010-02-09 03:39:12 UTC
The inconsistency has been fixed, whether it's best to parse links only or the full range of wikitext has not been resolved.
Comment 3 Siebrand Mazeland 2010-05-05 20:21:01 UTC
(In reply to comment #2)
> The inconsistency has been fixed, whether it's best to parse links only or the
> full range of wikitext has not been resolved.
This issue was fixed by no longer parsing the topics of the issues, so that the topics on Lqt pages on for example http://translatewiki.net/wiki/Project:Translator also look pretty ugly.

What's the final outcome, and why?
Comment 4 Andrew Garrett 2010-08-28 13:18:07 UTC
*** Bug 24683 has been marked as a duplicate of this bug. ***
Comment 5 Quim Gil 2013-03-21 16:07:25 UTC
There are many reports related to parsing or not parsing {{foo}}. Taking this as reference and raising its priority. 

The first problem to solve is documentation: what is the current behavior?

Then maybe we can fine tune that behavior based ons specific needs. Most of us will agree that rendering {{bar}} in titles is useful, although we can also agree that some limitation must be in place to avoid the rendering of full pages, or variables driving mad the tool.

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


Navigation
Links