Seeking suggestions for debugging conflicting plugins

[dltj]

I'm seeing a conflict between jinja2content and yaml-metadata. Here is the sequence:

1. Start with a fresh Pelican installation and add one article (see Article Markdown below)
2. Add the jinja2content plugin
3. Generate site and confirm that the macro loaded
4. Add the yaml-metadata
5. Don't add any other content, just clear the output directory and generate the site

The result after step 5 is that the text of the macro, not the expansion of the macro, is what is rendered.

I'm new to Pelican, so I haven't worked out how all of the internals work. Are there suggestions of where I should start looking to find the source of the conflict?

Edited to add: Both plugins are at the head version, e.g., git+https://github.com/pelican-plugins/yaml-metadata.git

Step 3 screen capture

Step 5 screen capture

Article Markdown

Title: 'This is a normal post'

Trying to insert the macro here.

{% from 'macro.html' import genurl %}
{{ genurl() }}

Did it work?

macro.html

{% macro genurl(string, force=False) %}
<h2>Got Here!</h2>
{% endmacro %}

[dltj]

Ah — we have a Highlander situation ("There can be only one"). Specifically, although signals.readers_init can have multiple classes attached to it, each is going to try to set readers.reader_classes[ext] to be its own Reader class.

Hmmm....

[dltj]

I created a Pelican plugin to do exactly that—combine YAMLMetadataReader and JinjaMarkdownReader in one Pelican Reader. This takes the content output of the YAML Metadata Reader and uses it as input to the Jinja Markdown Reader. It returns the content from JinjaMarkdownReader and the metadata from YAMLMetadataReader. (It discards the metadata returned from JinjaMarkdownReader, which should effectively be none.)

https://github.com/dltj/zygote-reader