Why store markdown version in 'post_content_formatted' column in DB?
From the looks of it, if I am not wrong, Markdown on Save Improved will soon make its way into Jetpack. It’s probably the one being used on WordPress.com as well.
But the problem remains. Certain edits (e.g. ‘Quick Edit’) delete the Markdown version of the post stored in
post_content_filteredcolumn in the database.
I see that it’s the intended behavior of
post_content_filteredcolumn, but in that case why use it at all? Why not some other column, that can store the Markdown version permanently? (Is it because, using any other column would make it difficult to replace Markdown/HTML in the editor when editing?)
Do you have any plans to “fix” this behavior?
- The topic ‘Why store markdown version in 'post_content_formatted' column in DB?’ is closed to new replies.