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

[alfredxing]

@parkr Nice catch! I'll see about fixing that up and just adding it as a Page.

[matthewmcvickar]

I’m not sure if I’m misunderstanding the status of this issue, but is there a workaround for this currently, or does the jekyll-archives plugin need to be fixed?

[alfredxing]

@matthewmcvickar Sorry for the wait; I've been quite busy recently with school. I'll get around to this as soon as I have some time!

[alfredxing]

Just looked into this again, and now I remember why I didn't append the archives to site.pages: if this was done, anyone iterating over site.pages (in the nav, for example) would see archive pages as well...
@parkr Any suggestions?

[parkr]

The only way to enforce this would be to render every item...

[alfredxing]

You mean render every page as necessary?

[DylanVann]

The markdownify filter might be useful for this.

{{post.content | markdownify}} or {{ content | markdownify}}, whatever fits.

[gdhnz]

While using markdownify does appear to render the markdown, it doesn't render {% highlight bash %}

[sumdog]

I had this same issue. I have an _include file for all my posts. For the archive layout, I just did the following:

{% for post in page.posts %}
  {% include post.html item=post markdown=true %}
{% endfor %}

and within my post include:

  {% if include.markdown %}
    {{ include.item.content | markdownify }}
  {% else %}  
    {{ include.item.content }}
  {% endif %}

Since generators are run before renders, this might be the only solution (unless you do the markdown step in the generation in jekyll-archives itself... haven't looked at the code to see how possible that is)

[gdhnz]

While the previous suggestion of an include works for markdown, it still doesn't render {% highlight bash %} blocks.

Is there a similar method like markdownify that does render code highlights? hilightify?

{{post.content | markdownify | hilightify }}

[MaximeKjaer]

Not to my knowledge. I've been able to get rid of the problem by downgrading from jekyll-3.0.0.pre.beta8 to jekyll-2.5.3 for the time being... (though that means going back to dealing with issue #2607 which was fixed in the beta 😥).

[nbolten]

This still happens with jekyll-2.5.3 and jekyll-archives 2.0.0. @MaximeKjaer, what is your setup where you can get post.content rendered from a jekyll-archives layout?

[nexocentric]

@DylanVann If content written in markdown needs to be run through a filter to be displayed properly, shouldn't that be added to the documents? Or is this thread actually not a question, but a bug?

[metachris]

Any feedback on this issue?

{{ post.content | markdownify }} works as a workaround for the markdown, but syntax is not highlighted.

Seeing this on jekyll 3.1.1

[fabacab]

Just a note to say I ran into this today, too. {{ page.content | markdownify }} works for me, too, though, so all things considered, pretty minor.

[OscarPellicer]

I was having this problem, where a post preview would (only in some pages) show unrendered liquid code from some includes I had

`

{{ post.content | strip_html | truncatewords:43 }}

`

Since I wasn't able to find a solution I included this quick and dirty fix at the end of every page, until I find something better:

<script> 
        $( ".remove-jekyll-js" ).each(function() {
            var post= $( this ).html();
            $( this ).html(post.replace(/\{\%.*?\%}/, "").replace(/\{\%.*?\.\.\./, "..."));
        });
</script>

This uses jquery and js to get rid of {% whatever %} and {% whatever ...
Maybe someone finds it useful in the meanwhile.

[breakingespanol]

I'm having this issue as well, however, part of the page is rendering but not all. Specifically, the unordered list is not rendering.

repo:
where: http://breakingespanol.com/about/
my page layout:

---
layout: default
---
<article class="page">
<h1>{{ page.title }}</h1>
<div class="entry">
{{ content }}
</div> `

[KendallPark]

Interestingly, my gh-pages site depends on page.content being the raw markdown of the page. Now it seems that gh-pages has "fixed" this, subsequently breaking my site, which requires raw markdown for Remark.js. Is there a way to get the raw, unprocessed markdown?

[ghost]

@KendallPark I don't think your problem is related to jekyll-archives however a solution for you is to add a generator plugin that adds a variable containing the raw markdown. Use this variable in place of page.content. However you'll have to build your site locally before pushing to Github Pages.

[groundh0g]

Sorry if this is off-topic, but I ran across a similar issue with a very simple fix.

My code to aggregate a list of book summaries looked like this:

{% for file in site.pages %}
    {% if file.path contains "books/" and file.path contains "/summary.md" %}
        {{ file.content }}
    {% endif %}
{% endfor %}

The content wasn't formatted. So I tried the markdownify solution and it became unformatted, raw HTML. That made me think it was being treated like a code block (indented by more than 4 spaces).

The following fixed it for me. (Note the unindented {{ file.content }} statement.)

{% for file in site.pages %}
    {% if file.path contains "books/" and file.path contains "/summary.md" %}
{{ file.content }}
    {% endif %}
{% endfor %}

[groundh0g]

@breakingespanol, when you wrap markdown in a <div/>, you'll see that behavior. Does the markdownify filter not fix it?

(eg. <div class='entry'>{{ content | markdownify }}</div>)

[2m]

Got bitten by this in https://github.com/akka/blog

Worked around with:

{% assign curlyend = '}' %}
{{ p.content | markdownify | strip_html | replace: "{% include JB/setup %", "" | replace: curlyend, "" | truncatewords: 30 }}

[alfredxing]

@2m Are you using jekyll-archives? I looked at your repo and it looks like you're using Jekyll Bootstrap, but I couldn't find Archives in your _config.yml anywhere.

[2m]

Hm. You might be right. I am not that experienced in jekyll. If you say that you could not find jekyll-archives in the project, then I am not using it. Sorry for the noise here. The problem described here looked similar enough to the one I was having, therefore I assumed my blog was using jekyll-archives for displaying post archive.

[ashmaroli]

Hello everyone!!
Is this still an issue while using Jekyll 3.7 / Jekyll 3.8 ? If yes, would you be able to provide a link to a minimal test repository that I can just clone and use..?

[wez]

I think this issue and jekyll/jekyll#6209 have some similarities in how they manifest. I'm using GH pages with no explicit configuration of jekyll-archives so perhaps this issue is not the best one to remain open to track this. I pushed wez/wezterm@b0f2edd which captures the state of the weirdness in case someone would like to dig in and resolve things. I have a workaround that I'm "OK" to stick with for now.

[trivedihiralm]

Running into similar issue.
markdownify did help with rendering the page correctly but my .md file has an HTML included in it.
{% include links.html %}

The links.html doesn't get rendered correctly for a few when the HTML files are getting generated.
Any tips on how to solve this?