Destroyed the markdown in our posts, two weeks and no update from developers

  • So it turns out that CoSchedule has a nasty little bug which strips markdown from posts. We’ve attempted to raise this with the developers directly to no avail, and even when they fix it, we will still have lost all of the markdown formatting from our content.

    I had always viewed reviews of CoSchedule with an air of skepticism knowing that they offer a discount on subscriptions for reviews, (they even mandate word count and the use of images in such pieces) bear this in mind when considering their now even costlier subscriptions.

Viewing 1 replies (of 1 total)
  • Anonymous User 202350

    (@anonymized-202350)

    Hi pixeldynamo,

    I’m terribly sorry about this. At the time of this post I’ve just pushed an update to the plugin (v2.3.4) which accounts for a particular Jetpack Markdown module behavior that we didn’t know was in place.

    To provide some context to the plugin conflict, when CoSchedule syncs a post to WordPress it triggers an anonymous update to the post. When Jetpack’s Markdown module is activated, all updates to a post clear the ‘content_post_filtered’ column unless it is intentionally repopulated with data. Jetpack accounts for this within WordPress, but CoSchedule’s anonymous update endpoint did not — generally the ‘content_post_filtered’ field (where the markdown is stored) is used for transient storage, so it wasn’t a case we anticipated.

    The plugin update 2.3.4 detects an active Jetpack Markdown module and prevents the clearing of the ‘content_post_filtered’ column.

    We sincerely apologize that data was lost in your blog with CoSchedule installed. Going forward we intend to treat Jetpack as core WordPress due to its popularity as a plugin.

Viewing 1 replies (of 1 total)
  • The topic ‘Destroyed the markdown in our posts, two weeks and no update from developers’ is closed to new replies.