Blockquotes using Markdown in a wiki [Solved]

It also seems that the definition list is not rendering either.

I noticed the plugin was released in 04. Is it possible that there are newer versions of Markdown that the current plugin does not support?

PHP Markdown Extra (forum thread) does definition lists, and I think it would also do blockquotes.

Yes, I did switch over to PHP Markdown Extra but I just can’t get the blockquote to render. I’ve even copied the code directly from John Gruber’s site!

Ok, so I just tested this and it outputs a blockquote perfectly. Can you let us know how you’re using it? Have you set it as that field’s formatting, or are you calling it in a template? Also, what exactly are you putting in your entry?

I did this:

> This is
> a blockquote

and it also worked without the space between the > and the text.

Also make sure you download a fresh copy of the plugin, as it has been updated since its initial release; and that’s the one I’m testing with, a fresh download as of today.

Lisa,

Here is the context:

I am using it in a wiki with the text formating for articles set to “Markdown”. Any time I use

> This is
> a blockquote

I just get

> This is > a blockquote

Aha, in the wiki. Back in a jiffy.

It’s probably not that big of a deal as I have just been using

<blockquote></blockquote>

instead. That works just fine.

You need to allow all HTML for this to work in the wiki. I was able to replicate your issue with “allow only safe html”.

I wonder why this would not fall into the “safe html” category.

Thanks for your help with this!

Ok, been chatting with Derek and I finally grok what is going on. <blockquote> is safe HTML, certainly (you can find this in core.typography.php if you are curious), however, Markdown uses > to indicate a blockquote. The template parser is converting the > to its character entity before Markdown ever gets involved. That’s why switching it to allow all HTML allows it to work.

You could hack the plugin to use a different notation for blockquotes, as one possible action. You could use a different plugin, of course.

Ah, that makes sense. I think I will just leave it with allowing all html as this wiki is not open to public additions. Only people within our organization will be able to change anything.

Thanks for the explanation.

As always - very helpful!

Keep in mind that even with Allow All HTML, user input is sanitized against “naughty” tags as well as XSS attacks. Mistakes or unwanted tags that slip in otherwise (such as layout-breaking closing divs) can typically be handled in wikis with the regular article moderation that happens in such environments.

Sounds good. Thanks for the note!