Markdown look+feel+parser but markup ends up as HTML/WP-macros in DB

  • Resolved abitofmind

    (@abitofmind)


    3 years, 3 months ago

    This important differentiation is missing in the description!

    I have not installed and tested this plugin.

    But from reading the info available and looking at the demonstration video, I think this is what is happening behind the scenes.

    This is a very important fact to know, whether pages edited with this Editor end up in Markdown syntax in the database, and hence always need to run their own parser & renderer, or whether Markdown look & feel is only used as the presentation form in the editor, but behind the scene this gets transformed to standard HTML and WordPress macros (encoded as HTML comments).

    Please be clear about this for your visitors. Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support sabbirsam

    (@sabbirsam)

    Hi @abitofmind

    Markdown editor is Markdown look & feel which is only used as the presentation form in the editor.

    Behind the scene this gets transformed to standard HTML and WordPress macros (encoded as HTML comments).

    We will add the part to our description.

    Thanks

    Thread Starter abitofmind

    (@abitofmind)

    Thanks for confirming this. And glad that this info will make it into the description.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Markdown look+feel+parser but markup ends up as HTML/WP-macros in DB’ is closed to new replies.