Symphony.

I switched my ‘vanilla’ Markdown Text formatter to ‘Markdown Extra (Smartypants)’ because I needed the ID’s in headings feature of Markdown Extra.

## Heading Level2 {#my-heading-id}

.. should be converted to <h2 id="my-heading-id">Heading Level2</h2> but it is not. The {#my-...} is just left as part of the H2.

I tried various ways of adding the ID but it simply seems Markdown Extra does not apply.

I’ve read some threads on this forum re: Javascript and   but these do not seem to apply (JS does not convert the value and no  ’s are added, I checked the Db).

Any ideas?

PS: It might be handy to document the exact differences between the Text Formatters. These are not all completely obvious to me. E.g. I would expect HTML content to be ‘purified’ in the vanilla Markdown also, so why need the HTML Purify version? etc.

Did you re-save the affected entries? AFAIK the formatted values are only created when you save an entry and then stored in the database.

You could also create the id-attributes in the XSLT template with some ninja technique.

Edit: Well, you must have saved the entry when you added the markdown plus syntax to add the id :)
So I don’t know what’s going on.

This is a known bug I raised recently.

#396 Markdown Extra does not work

@klaftertief I did. I even changed the TF back to ‘None’, saved, and then back to Markdown Extra again.

@nickdunn Ok, a ‘known bug’ therefore? This means I need to (temporarily) find a workaround. (Simple enough, it’s no biggie…)

Will this mean the bug will be addressed no sooner than Symphony 2.2, or will there be a 2.1.2?

Thanks for letting me know.

Your comments on Github seem to suggest this will be picked up with a 2.2 release. Any thoughts on when that might be?

In the mean time I can fix it myself but I’d rather not ‘patch’ the Core too much.

No idea when, but I would expect the team to go through the issue tracker and close outstanding bugs for a 2.2 release, so it would be fixed.

great. In the meantime it’s a tiny fix.