Header Not Working

wuf31 - April 30, 2009 - 10:26
Project:Markdown filter
Version:6.x-1.x-dev
Component:Documentation
Category:task
Priority:normal
Assigned:Unassigned
Status:active
Description

## Header is not turning into

Header

as one would expect.
It works well with Markdown Preview though..

Help ?

#1

azinck - September 11, 2009 - 00:51

bump -- I'm seeing this problem as well.

#2

adam_b - September 12, 2009 - 20:26

Subscribe - me too. I tried both Setext and atx - no luck.

#3

azinck - September 14, 2009 - 14:20

I take it back...mine is working fine. I had my line-break converter filter arranged after the Markdown filter and that was causing issues. If you're using the line break converter with Markdown the Markdown filter MUST be positioned after the line-break converter filter.

#4

wuf31 - September 16, 2009 - 15:40

...
This filter arrangement should have a handbook on it's own.
I'm pretty sure this is not the first time i've had a headache with it.
It's time consuming, figuring out the order of the input filter.

#5

adam_b - September 16, 2009 - 21:10

Sorry, but my Markdown filter *is* positioned after the line-break converter filter, and the headers still aren't working. I tried turning off the line-break converter, but that didn't help either.

#6

John Magolske - September 17, 2009 - 23:06

I too was also having a lot of trouble with getting Markdown to work. In addition to the Headers not being rendered, there was an issue with line breaks being converted to <br> tags -- not standard markdown behavior. *Finally* I arrived at a filter ordering that works out! I found the line-break converter had to be turned off, which makes sense as Markdown itself is supposed to take care of line breaks. I'm using the filters listed below, in the order listed:

HTML filter
HTML corrector
Typogrify
Markdown
URL filter

With the line-break filter at the top of that list, everything seemed to be working except the unordered lists were not rendering (all the *'s were just dumped out into one line), so I ditched it. Also, there seems to be some subtle difference when Typogrify is ordered after Markdown. Having it in the order shown above seems to work better.

BTW, this contradicts what's said in the Markdown module's README.txt:

For best security, ensure that the HTML filter is after the Markdown filter on the
"Reorder" page of the input format and that only markup you would like to allow
in via HTML and/or Markdown is configured to be allowed via the HTML filter.

source:
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/markdown/RE...

But when the HTML filter is ordered after the Markdown filter, the markup doesn't get rendered into html at all.

#7

adam_b - September 18, 2009 - 09:31

My hero!!! This finally works for me.

I was resigning myself to spending a whole evening testing different filter orders, but thanks very much for doing it for us.

#8

wuf31 - September 19, 2009 - 06:05
Component:Code» Documentation
Category:support request» task

Documentation update will be needed..
Thanks a lot, John :)

 
 

Drupal is a registered trademark of Dries Buytaert.