post.content markdown not rendered

[gdhnz]

I'm displaying full posts in my archives but the post is displaying the raw markdown and not being rendered.

[gdhnz]

Using {{ content }} also doesn't show the content at all.

[parkr]

Ah, I see. Generators are called before the render process is complete. That said, this should work nevertheless. Can you post a link to your site? What does your archive template look like? What version of Jekyll are you using?

[gdhnz]

I haven't got the site live yet as there's still a lot of other things I need to first.

Here's the archive layout I'm using with the Jekyll 2.5.2.

---
layout: default
---

<h2 class="archive-title">Archives: {{ page.title | date: '%B %Y' }}</h2>
{% for post in page.posts %}
<article> 
    <header class="entry-header">
        <h2 class="entry-title">
            <a href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a>
        </h2>
        <time class="published" datetime="{{ post.date }}" pubdate="">
            <a href="{{ post.url | prepend: site.baseurl }}">{{ post.date | date_to_string }}</a>
        </time>
    </header>

    <div class="entry-content">
        {{ content }}
    </div>
</article>
{% endfor %}

Using {{ content }} instead of {{ page.content }} doesn't return anything.

[parkr]

Yeah it has to be post.content instead of content or page.content.

[gdhnz]

and we're back to my original statement. When I use post.content, none of the markdown or liquid tags are rendered.

[parkr]

and we're back to my original statement. When I use post.content, none of the markdown or liquid tags are rendered.

What does that mean? Plain text? Or a code block? Can you paste a screenshot?

[gdhnz]

Here's the screenshot.

[alfredxing]

Is this not the case for any post/page listing? post.content contains the raw input, not the processed output.

[gdhnz]

Here's the snippet for my index.html file that displays everything correctly.

<div class="listing">
    {% for post in paginator.posts %}
    <article> 
        <header class="entry-header">
            <h2 class="entry-title">
            <a href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a>
            </h2>
            <time class="published" datetime="{{ post.date }}" pubdate="">
            <a href="{{ post.url | prepend: site.baseurl }}">{{ post.date | date: '%B %d, %Y' }}</a>
            </time>
        </header>
        <div class="entry-content">
            {{ post.content }}
        </div>
    </article>
    {% endfor %}
</div>

[davepeck]

I'm running into this bug too -- {{post.content}} in an archive page loop does not process through markdown -- so you end up getting the raw markdown text instead of intended HTML.

[parkr]

I'm running into this bug too -- {{post.content}} in an archive page loop does not process through markdown -- so you end up getting the raw markdown text instead of intended HTML.

Generators are run before the render step. https://github.com/jekyll/jekyll/blob/master/lib/jekyll/site.rb#L51-L58

[davepeck]

Understood, thanks!

I'm wondering where the solution lies. It feels like the current behavior is undesirable. Is this something that needs to be filed against Jekyll itself -- an improvement for Generators for future consideration? Or is there a way to improve jekyll-archives here? Thanks.

[parkr]

The solution is to allow Jekyll to do the rendering itself. The jekyll-paginate process does this by appending a Page to site.pages and letting Jekyll do its thing. From a cursory glance at the source code here, the render process is taken care of here, which would yield this error. /cc @alfredxing