Plugin Author
Ha Ho
(@hoducha)
You should deactivate the Markdown module from Jetpack settings.
Explanation: The plugin uses Jetpack Markdown module for parsing and saving contents. The module is included in the plugin in order to make it works independently. So, you could not activate the plugin if the Jetpack Markdown module is activated.
Maybe the plugin could detect another version of Jetpack Markdown and showed an alert message.
Plugin Author
Ha Ho
(@hoducha)
@li-an: I will update the plugin to detect if Jetpack Markdown is activated. But I recommend that you should activate only one Markdown plugin to prevent unexpected errors.
@ha Ho,
Thanks for your help. I disabled the jetpack module and I was able to activate the plug-in.
Plugin Author
Ha Ho
(@hoducha)
You’re welcome. I’ll mark this ticket as resolved and add the code to detect if Jetpack Markdown is activated in the next release.
Thanks, but you should probably make a note of this in the installation instructions and the FAQ. Seems pretty important and I didn’t even notice it, so after just installing it and activating it after Jetpack (which you mention should be activated first), I got into this error state.
I’ve just run into this as well. Reading the plugin I thought you had to install and activate the Jetpack plugin Markdown module.
