Update if another Markdown plugin isn't playing well with Markdown on Save<\/p>","1.1.5":"
Update to fix issues with slashes disappearing.<\/p>","1.1.4":"
Upgrade to use Markdown over XML-RPC (use to enable it)<\/p>","1.1.3":"
Upgrade to fix the bug that caused "titles" in links to fail parsing and to disable the visual editor in Markdown mode<\/p>","1.1.2":"
Upgrade to fix the bug that caused "titles" in links to fail parsing<\/p>","1.1.1":"
Prevents the meta box from mistakenly appearing on the Dashboard<\/p>","1.1":"
Enables the Markdown option for all content types, instead of limiting it to posts<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0","1.1","1.1.1","1.1.2","1.1.3","1.1.4","1.1.5","1.2","1.2.1","1.3.0","1.3.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3081322,"resolution":"1","location":"plugin"}},"screenshots":{"1":"The Markdown logo you click to designate a post as containing Markdown. This is the only UI for the plugin!"},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[1975,4608],"plugin_category":[46],"plugin_contributors":[77745],"plugin_business_model":[],"class_list":["post-10673","plugin","type-plugin","status-publish","hentry","plugin_tags-formatting","plugin_tags-markdown","plugin_category-editor-and-writing","plugin_contributors-markjaquith","plugin_committers-markjaquith"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/markdown-on-save.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/markdown-on-save\/trunk\/screenshot-1.png?rev=3081322","caption":"The Markdown logo you click to designate a post as containing Markdown. This is the only UI for the plugin!"}],"raw_content":"\n
This plugin allows you to compose content in Markdown on a per-item basis. The markdown version is stored separately (in the Note: this plugin assumes you're using the Classic editor.<\/p>\n\n\n Upload the Activate the \"Markdown On Save\" plugin in your WordPress administration interface<\/p><\/li>\n Create a new post with Markdown, and click the Markdown logo in the publish metabox (see screenshot).<\/p><\/li>\n Done! Now that post can be edited using Markdown, but will save as processed HTML on the backend.<\/p><\/li>\n<\/ol>\n\n\n Please refer to this resource: [http:\/\/michelf.com\/projects\/php-markdown\/extra\/](PHP Markdown Extra).<\/p><\/dd>\n Your post will no longer be interpreted as Markdown, you will be returned to the normal editing experience.<\/p><\/dd>\n Just deactivate it. The Markdown version is stored separately, so without the plugin, you'll just revert to editing the HTML version.<\/p><\/dd>\n\n<\/dl>\n\n\npost_content_filtered<\/code> column), so you can deactivate this plugin and your posts won't spew out Markdown, because HTML is stored in the post_content<\/code>, just like normal. This is also much faster than doing on-the-fly Markdown conversion on every page load. It's only done once! When you re-edit the post, the markdown version is swapped into the editor for you to edit. If something external updates the post content, you'll lose the Markdown version.<\/p>\n\n\n
markdown-on-save<\/code> folder to your \/wp-content\/plugins\/<\/code> directory<\/p><\/li>\n\n
How do I use Markdown syntax?<\/h3><\/dt>\n
What happens if I click the Markdown logo again?<\/h3><\/dt>\n
What happens if I decide I don't want this plugin anymore?<\/h3><\/dt>\n
1.3.1<\/h4>\n\n
\n
1.3<\/h4>\n\n
\n
1.2.1<\/h4>\n\n
\n
1.2<\/h4>\n\n
\n
1.1.5<\/h4>\n\n
\n
stripslashes()<\/code> error<\/li>\n<\/ul>\n\n1.1.4<\/h4>\n\n
\n
1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
1.1<\/h4>\n\n
\n
1.0<\/h4>\n\n
\n