Disabling Markdown (Classic Editor) on specific page templates

@argumentum0 I don’t know a way to do that, but if you were creating custom post types instead, you’d have to add code to enable markup support:
https://jetpack.com/support/markdown/

So, depending on the function of these certain page templates, would you consider adding it as a CPT instead, and leaving the markup code out of them?

@supernovia, thanks for answering.

Unfortunately, adding a CPT would complicate things too much for me. I will tell you my situation, and maybe you can give me other suggestions.

Apparently, my problem is related to some issue on how the Markdown module works when the wpautop function is disabled.

I have the wpautop function disabled on some specific page templates. But, when I use these templates, the Markdown module removes all the <p></p> tags of the page (tags that were manually inserted, of course, since wpautop is disabled on these templates). These tags shouldn’t be removed.

And, when I use the page templates which have the wpautop function enabled, the Markdown module apparently doesn’t touch the <p></p> tags I have manually inserted, but wpautop automatically adds lots of other <p></p> tags in the page.

I want to disable the Markdown module on the same page templates I have the wpautop function disabled. Basically, I want nothing changing my text on these specific page templates.

I hope this is something possible.

• This reply was modified 5 years, 6 months ago by Argumentum.
• This reply was modified 5 years, 6 months ago by Argumentum.

Sorry to hear it. I don’t really have a great answer for handling this (aside from using a CPT), and it’s outside the scope of support we can offer. But if you do find an answer, please do share it here.