Last modified: 2010-05-15 15:48:21 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 8722 - Headings from tranclusion not rendered
Headings from tranclusion not rendered
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.9.x
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-21 16:17 UTC by Ben
Modified: 2010-05-15 15:48 UTC (History)
0 users

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


Attachments

Description Ben 2007-01-21 16:17:57 UTC
When I include my page in another, there is not the Wiki's rendering, for exemple, the ==My Text== stay 
like that.

Thanks to you.
Comment 1 Rob Church 2007-01-21 17:53:15 UTC
1. Upgrade to 1.9.0 proper
2. Please provide the markup for the page being included, and the page including
it (as attachments to this bug)
Comment 2 Ben 2007-01-21 18:07:17 UTC
Excuse me, but I don't understand your second phrase ... (I'm french and poor in
English ^^)

In my page, I use a template, which insert another page, like that : {{{{{page}}}}}

And when the page is included, my text, which looks like ===My Text=== stay like
that, it is not bigger and bold.

Thanks.
Comment 3 Rob Church 2007-03-20 22:04:26 UTC
Heading markup needs to be at the start of a line. Check that the template is at
the start of a new, blank line.

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


Navigation
Links