Title: Markdown not interpreted Last modified: November 5, 2020 --- # Markdown not interpreted * Resolved [Li-An](https://wordpress.org/support/users/li-an/) * (@li-an) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/) * Hello, for some reason, on one of my site, Markdown is no more translated in HTML. I deactivated all other plugins without any result. Strangely, it works on other sites on the same hosting. So it may come from the database but repairing and optimizing does not change anything. I use Classic Editor in HTML edit mode. - This topic was modified 5 years, 7 months ago by [Li-An](https://wordpress.org/support/users/li-an/). - This topic was modified 5 years, 7 months ago by [Li-An](https://wordpress.org/support/users/li-an/). Viewing 15 replies - 1 through 15 (of 25 total) 1 [2](https://wordpress.org/support/topic/markdown-not-interpreted/page/2/?output_format=md) [→](https://wordpress.org/support/topic/markdown-not-interpreted/page/2/?output_format=md) * Plugin Support [fresatomica](https://wordpress.org/support/users/fresatomica/) * (@fresatomica) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13625281) * Hi there! * What is the URL of the site where this happens? * > I deactivated all other plugins without any result. * I understand that when you deactivate **all plugins** the issue disappears and it reappears when you activate Jetpack as the only active plugin on the site. Is that correct? * Thread Starter [Li-An](https://wordpress.org/support/users/li-an/) * (@li-an) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13625383) * Here is the URL [https://www.li-an.fr/](https://www.li-an.fr/). * > I understand that when you deactivate all plugins the issue disappears and > it reappears when you activate Jetpack as the only active plugin on the site. > Is that correct? * No, sorry for my bad english : it does not work correctly even if Jetpack is the only plugin activated. * I reactivated the old jMarkdown (out of depot now and Jetpack is not running with jMarkdomn) plugin I used before Jetpack and with this one, HTML is correctly generated (but Markdown version seems to be lost – after saving content, Markdown is not showing). * Plugin Contributor [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13627586) * Would you please share some of the markdown you’re trying to use? * Thread Starter [Li-An](https://wordpress.org/support/users/li-an/) * (@li-an) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13628594) * `## Title` * This won’t work. No Markdown is working. * Plugin Contributor [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13631747) * Hm, I’m having no trouble with that. * Does it work if you deactivate the Classic Editor plugin? * Thread Starter [Li-An](https://wordpress.org/support/users/li-an/) * (@li-an) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13632590) * Markdown block is working. * Plugin Contributor [Dan (a11n)](https://wordpress.org/support/users/drawmyface/) * (@drawmyface) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13639386) * Glad to hear that. Are you ok to keep using the markdown block instead of the classic editor? * Thread Starter [Li-An](https://wordpress.org/support/users/li-an/) * (@li-an) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13639495) * No. Working with Gutenberg gives me headaches. I don’t like it at all and I cannot work efficiently with it. * I tried another Markdown plugin – [https://fr.wordpress.org/plugins/wp-githuber-md/](https://fr.wordpress.org/plugins/wp-githuber-md/)– and met the same problem as **JPMarkdown**: in **wp_posts.post_content_filtered**, I’ve got the HTML version and not the Markdown version. So all these three plugins meet problems on my site. **JP Markdown** and **WP githuber MD** do not “remember” Markdown version of the content and Jetpack’s Markdown Module does not generate the HTML version. * And all the three works correctly on same hosting and same database for other sites. A complete mystery to me. * Discussion about WP Githuber MP problem here [https://github.com/terrylinooo/githuber-md/issues/88](https://github.com/terrylinooo/githuber-md/issues/88) and I’m not the only one. But I cannot know if the users have tried Jetpack’s Module. - This reply was modified 5 years, 7 months ago by [Li-An](https://wordpress.org/support/users/li-an/). - This reply was modified 5 years, 7 months ago by [Li-An](https://wordpress.org/support/users/li-an/). * [Ryan C.](https://wordpress.org/support/users/ryanc413/) * (@ryanc413) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13645531) * Thanks for the additional information. I had a look at your site and noticed that Jetpack is not connected. Just to clarify, is that intentional? * If not, could you please try reconnecting Jetpack on your site? That will help us troubleshoot the Markdown issue further. * Thread Starter [Li-An](https://wordpress.org/support/users/li-an/) * (@li-an) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13645585) * I deactivated it because of the problem (I could not work anymore in Markdown). I just reactivated it and, surprise, I’ve got the HTML showing after saving. So, Jetpack is now acting like the two other plugins. * A question: when the problem occurred, my first thought was to check database size and I discovered that my files/database size was to important for my hosting plan. I cleaned some files without any result for Jetpack. Yesterday, I cleaned more files and, as I said, HTML version is now generated by Jetpack. Do you think I should try to clean more files? (but in this case, why does Jetpack works on same hosting plan for other sites ?). * Plugin Contributor [Dan (a11n)](https://wordpress.org/support/users/drawmyface/) * (@drawmyface) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13648318) * > Do you think I should try to clean more files? (but in this case, why does > Jetpack works on same hosting plan for other sites ?). * I’m not sure if this issue would have been caused by exceeding your host’s file storage limit, but in general it’s a good idea to remove any files you don’t need. * Let us know if you have any more trouble. * Thread Starter [Li-An](https://wordpress.org/support/users/li-an/) * (@li-an) * [5 years, 7 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13648404) * Well, the problem is not solved. As I said, the Markdown version is not saved in **wp_posts.post_content_filtered** so it’s half working. Like the other Markdown plugins. * Plugin Contributor [Dan (a11n)](https://wordpress.org/support/users/drawmyface/) * (@drawmyface) * [5 years, 6 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13653355) * Post content is not stored as Markdown in the database, it is interpreted in the editor, and saved as HTML. Having said that, you shouldn’t see HTML in the editor unless you are editing in HTML mode. * Can you share a screenshot of your editor with us? We have helpful instructions here: * – [https://en.support.wordpress.com/make-a-screenshot/](https://en.support.wordpress.com/make-a-screenshot/) * You can take the screenshot, then upload it to your site, so you can share the link here. * Thanks * Thread Starter [Li-An](https://wordpress.org/support/users/li-an/) * (@li-an) * [5 years, 6 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13653393) * Well, I’m working in HTML editor (Classic Editor)… as I always did for years now. And it works in th same configuration on my other sites. I’m very surprised you say Post content in not stored as Markdown in the database as it’s exactly the feature of original plugin (and I made a post about this on my plugins reviews blog) and it’s saved as Markdown as you can see on this capture: * [⌊2020-11-12-11-47-25⌉⌊2020-11-12-11-47-25⌉[ * [Ryan C.](https://wordpress.org/support/users/ryanc413/) * (@ryanc413) * [5 years, 6 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/#post-13656597) * Thanks again for the information and screenshot. It does indeed look that he Markdown in question is being stored in your database. * As a next step, I’d like to ask a few clarifying questions to ensure we understand the issue: 1. Does this issue occur on regular posts or a custom post type? 2. Does this issue occur when you create a completely new post? 3. Does this issue occur when you edit an existing post? * Please let us know about the above and we’ll go from there! Viewing 15 replies - 1 through 15 (of 25 total) 1 [2](https://wordpress.org/support/topic/markdown-not-interpreted/page/2/?output_format=md) [→](https://wordpress.org/support/topic/markdown-not-interpreted/page/2/?output_format=md) The topic ‘Markdown not interpreted’ is closed to new replies. * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237) * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/) * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq) * [Support Threads](https://wordpress.org/support/plugin/jetpack/) * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/) * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/) ## Tags * [markdown](https://wordpress.org/support/topic-tag/markdown/) * 25 replies * 7 participants * Last reply from: [Dan (a11n)](https://wordpress.org/support/users/drawmyface/) * Last activity: [5 years, 6 months ago](https://wordpress.org/support/topic/markdown-not-interpreted/page/2/#post-13707445) * Status: resolved