Support » Plugin: Markdown on Save Improved » Preview is markdown text, not the converted html

Viewing 12 replies - 1 through 12 (of 12 total)
  • When the post is saved and published, the rendering is correct html.

    I found that the preview will not render markdown to html when the post is in published state. i.e. when I re-edit an old post and preview.

    Are there any plans to fix this? Other than this (big) annoyance, Markdown on Save improved is the best plugin for my needs!

    Plugin Author Matt Wiebe


    navarroj: it works fine for me. WP version, MoSI version?

    It’s most likely a plugin conflict.

    wordpress 3.5.2
    MoSI 2.4.2

    Same here: wordpress 3.5.2, MoSI 2.4.2

    Plugin Author Matt Wiebe


    In any testing I do with both of those versions, previews show converted Markdown (as they should).

    Maybe try deactivating all your other plugins and/or a different browser?

    I think I’ve found the cause of the bug. I tried disabling all plugins (except for “Options Framework” which, for some reason, seems impossible to disable).

    If you try to edit and preview an already published post, then “preview changes” shows the markdown instead of the converted HTML, but for a new post (or even just changing the status of an already published post back to “draft”) then “preview” will do the correct thing, interpret and render the Markdown as expected.

    I’ve tried this both on Chrome and Safari with exactly the same results, so I guess the browser doesn’t have much to do with it.

    I’m encountering the same problem. Preview works fine, until a post is scheduled or published. After that, the preview breaks.

    Plugin Author Matt Wiebe


    navarroj, thanks for finding where the bug was happening, and apologies for taking a long time. This is fixed in MoSI 2.4.4, which is now live.

    I think I have(had?) the same problem, and as a work around selected the option “Disable Markdown formatting” which seemed to help.

    However, I have a problem where my subscriber emails contain a preview with Markdown. Does selecting the option above cause the main article to be stored in markdown?

    Now the problem is fixed (I think I may have only ever used 2.4.4 as I only started blogging mid December) if I deselect that option will everything sort itself out and I’ll get html in the database & emails?

    I’ve just tried deselecting the option. i.e. Enabling markdown formatting on one of my posts:

    All is well, except the code blocks. They have spurious <p>s. So is there an incompatibility between this plugin and SyntaxHighlighter Evolved?

    I’m also using: Typewriter – Markdown for WordPress
    would that cause any issues?

    Thanks for any help. I can start a new thread if you prefer.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Preview is markdown text, not the converted html’ is closed to new replies.