Title: PHP Markdown's issue with the way WordPress processes text
Last modified: August 20, 2016

---

# PHP Markdown's issue with the way WordPress processes text

 *  Resolved [Aahan Krish](https://wordpress.org/support/users/aahan/)
 * (@aahan)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/php-markdowns-issue-with-the-way-wordpress-processes-text/)
 * PHP Markdown has a small problem with the way WordPress processes text, which
   I noticed in the upcoming WordPress flagship theme [Twenty Thirteen](http://core.trac.wordpress.org/browser/trunk/wp-content/themes/twentythirteen).
 * Wondering if the issue could be fixed on PHP Markdown’s end, I shared a small
   bug report with the author: [https://github.com/michelf/php-markdown/issues/73](https://github.com/michelf/php-markdown/issues/73)(
   I described the issue in detail there, please take a look.)
 * The issue persists with the plugin too (obviously, as it uses PHP Markdown). 
   Any idea as to how this can be fixed?
 * [http://wordpress.org/extend/plugins/markdown-on-save-improved/](http://wordpress.org/extend/plugins/markdown-on-save-improved/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Matt Wiebe](https://wordpress.org/support/users/mattwiebe/)
 * (@mattwiebe)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/php-markdowns-issue-with-the-way-wordpress-processes-text/#post-3576644)
 * Aahan, this is an issue with the assumptions that WordPress makes about the state
   of its content, and how MoSI works.
 * WordPress assumes that there will be no `p` tags (since that’s the way WP normally
   does things) and that’s the assumption that Twenty Thirteen is making when it
   appends the date to an `aside` post format. It thinks that the date will simply
   be caught up in the last paragraph, but instead, since MoSI creates `p` tags,
   it winds up outside of the last paragraph.
 * This could be worked around if need be, but it’s not really a plugin bug.
 *  Thread Starter [Aahan Krish](https://wordpress.org/support/users/aahan/)
 * (@aahan)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/php-markdowns-issue-with-the-way-wordpress-processes-text/#post-3576649)
 * Well, do you know any work around Matt? [I tried](https://github.com/michelf/php-markdown/issues/73)
   in vain.
 *  Plugin Author [Matt Wiebe](https://wordpress.org/support/users/mattwiebe/)
 * (@mattwiebe)
 * [13 years, 1 month ago](https://wordpress.org/support/topic/php-markdowns-issue-with-the-way-wordpress-processes-text/#post-3576651)
 * Asking the Markdown Extra author to fix this is the wrong approach. It’s not 
   a problem with Markdown Extra, it’s the clash of assumptions I already outlined
   above. Basically you need to strip the `p` tags created by Markdown, and then
   re-add the `wpautop` filter that MoSI removes.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘PHP Markdown's issue with the way WordPress processes text’ is closed
to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/markdown-on-save-improved_f4f4f4.
   svg)
 * [Markdown on Save Improved](https://wordpress.org/plugins/markdown-on-save-improved/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/markdown-on-save-improved/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/markdown-on-save-improved/)
 * [Active Topics](https://wordpress.org/support/plugin/markdown-on-save-improved/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/markdown-on-save-improved/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/markdown-on-save-improved/reviews/)

## Tags

 * [markdown](https://wordpress.org/support/topic-tag/markdown/)

 * 3 replies
 * 2 participants
 * Last reply from: [Matt Wiebe](https://wordpress.org/support/users/mattwiebe/)
 * Last activity: [13 years, 1 month ago](https://wordpress.org/support/topic/php-markdowns-issue-with-the-way-wordpress-processes-text/#post-3576651)
 * Status: resolved