Why the need to store the markdown version at all?

  • Just a quick question, why is there a need to store the markdown version? I would have thought 1) conversion to HTML 2) Storage of the HTML’d version in post_content would be a far more efficient way of doing it.

    Just wondering why there is a need to also keep the markdown version in post_content_filtered? What benefit is there to keeping a copy of the markdown version?

    https://www.ads-software.com/plugins/markdown-on-save-improved/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Matt Wiebe

    (@mattwiebe)

    So that you can continue editing in Markdown, even after you’ve saved a draft or published a post.

    Thread Starter Henry Wright

    (@henrywright)

    Thanks. That makes sense! So what happens in the case of comments? I notice there isn’t a comment_content_filtered column?

    Thread Starter Henry Wright

    (@henrywright)

    Just noticed markdown isn’t supported in comments. Thank again for your answer

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Why the need to store the markdown version at all?’ is closed to new replies.