Plugin always adds e-content div to post content. Should it?

[snarfed]

Plugin always adds e-content div to post content. Should it?

[janboddez]

Just FYI: What I do in my theme (or rather, plugin, but a theme could do the same) is I check if there's a .e-content in the post content already and only add the class if there isn't. (For some post types, it makes sense to have a, e.g., reply context outside of .e-context, and since---in my case---both are part of my post content I can't just add an overall e-content class. Hence the check.)

But I also completely override the Micropub post content in a filter callback, so ... That could work too, at least temporarily. Just remove the div in a filter.

[dshanske]

There's a setting that disables it entirely which my Post Kinds plugin turns on... I have some ideas I might pursue though.

[snarfed]

FWIW, I debugged this a bit more just now, and it's not specific to HTML content or JSON input, evidently the plugin always does this when it creates posts. Eg a form-encoded micropub request with content=fooey results in this content HTML:

<div class="e-content">
fooey
</div>

[snarfed]

(I don't actually know what should happen here! Just adding info for now.)