Markdown summary should not include content footnote #885
Markdown instance carries state for subsequent uses. Content
This PR adds a
Markdown instance carries state for subsequent uses. Content and summary parsing is done with the same instance. Since footnotes are processed with an extension and stored as state, content footnote is duplicated for summary. This PR adds a ``.reset()`` call before summary parsing to clear the state. It also adds a test case with footnotes.
None of the commenters here have specified which Pelican version is being used. As noted at the top of this issue, this fix is marked with the 3.3 milestone, so if you're using the current 3.2.x release, then of course you're going to see the previous (unfixed) behavior. If, on the other hand, the comments above are in reference to the current master, then please indicate that explicitly so we can determine if further action is warranted.