Markdown plugin broken/outdated

[rakaur]

I love the Markdown syntax and such, but (on WordPress 1.2) it appears to be mostly broken. Reference-style links don't work at all, and if you use any HTML (I frequently add <acronym> tags instead of constantly updating the acronym plugin) you get a giant amount of '<' symbols at the beginning of posts. Perhaps the plugin is just outdated to the current specification? Or perhaps it could be my WordPress style (dots), but I don't think that'd have anything to do with post filtering...

[Zarniwoop]

I already posted a bug fix to the Beta-Forum some time ago, but it is still not fixed in CVS.
However I also mailed the orignial author of PHP-Markdown since he had the same bug and he fixed it and -- much better -- added native support as a WP plugin.
Maybe it would be the best way to commit the newer version to CVS.
You can find the upgraded plugin at <a href="​http://michelf.com/projects/php-markdown/">​http://michelf.com/projects/php-markdown/</a>

After I installed the plugin, it did hard linebreaks for each line ending with a return (not the normal Markdown behaviour which requires two spaces before the return for hard linebreaks) but I will have a look at it and mail the author for a bug fix.

edited on: 06-14-04 03:14

It was a little problem with removing and adding filters and I already got an email, that it will be fixed in the next release (he accidentialy removed "wptexturize" instead of "wpautop"). After changing this, it works fine. Maybe it would be a better idea not to apply Markdown to the comment text (and use the standard wpautop filter instead) because the linebreak behaviour of Markdown appears to be really strange, if you don't know how it works.

edited on: 06-14-04 16:53

[rakaur]

UL and OL appear to be broken as well.

Using something like:

• hi
• hi
• hi

Or:

1. hi
2. hi
3. hi

Just outputs a paragraph tag with br's.

edited on: 06-14-04 23:29

edited on: 06-14-04 23:30

[Zarniwoop]

The bugfix for the original Markdown included with WP 1.2 can be found
at ​http://wordpress.org/support/6/6675 . The main problem is that Markdown fails when wptexturize is called first. After these changes it should work.

However I attached a modified version of the new php-markdown 1.0b7 with the bug fixed, filters applied correctly and comment formatting turned off by default (left to wpautop). I tested the whole syntax cheatsheet which can be found at Michel's site: ​http://michelf.com/projects/php-markdown/dingus/ and all works fine .

edited on: 06-15-04 02:59

[rakaur]

Thanks very much. :)

After a night of having things stolen from me this was a good reminder that not all people suck.

[matt]

Just upgraded markdown

[downloadbook]

Nothing.