I think I’ve contacted support once before about this but, well, I obviously still have the problem.
Yes, we’ve talked about this before.
This could be a plugin compatibility issue. Jetpack’s Markdown module doesn’t store any markdown content in the post_content row of your database. That row is used by WordPress to store your post content, and by your theme when accessing your post content to display it on the site.
Instead, Jetpack saves all your Markdown in a post_content_filtered row, and then converts that markdown to HTML and saves that HTML into post_content.
This way, if you ever decide to deactivate Jetpack, you don’t end up with raw Markdown code displayed in your posts. Jetpack never saved raw markdown in post_content, and your site can consequently continue to get its post content from that row, knowing it’s going to be HTML only.
Your previous plugin apparently didn’t follow the same rules. And if it didn’t save any content in post_content_filtered, Jetpack wouldn’t know to convert content into HTML.
However, if you were to edit an existing post and save it, Jetpack should start saving Markdown and converting it. Could you give that a try, and let me know how it goes?
Could you also let me know what happens when you write a brand new post? Does the Markdown module work there?
I too am having this problem. I activated Markdown via Jetpack and it reports all is hunky-dory. I go to Settings -> Writing and there is no “Use Markdown to post” checkbox. There is a “Use Markdown to comment” checkbox under Settings -> Discussion. If I create a new post and click on Text and paste some Markdown from Typora, my post looks like Markdown source code when I click on Visual. No rendering at all. I have disconnected/reconnected Jetpack numerous times. I have uninstalled and reinstalled it three times.
Markdown no workee.
My site is http://www.echenique.com
Any clues?
