Possibility to do a next / prev based on the content type?

[mpas]

When trying to implement Prev / Next for a specific content type i run into a problem when i have another content type like for exampe pages.

        {{if .Next}}
        <li><a class="previous" href="{{.Next.Permalink}}">← {{.Next.Title}} </a></li>
      {{end}}
      {{if .Prev}}
        <li><a class="next" href="{{.Prev.Permalink}}">{{.Prev.Title}} →</a></li>
      {{end}}

This results in the fact that 'post' and ' page' contenttypes are mixed. Is there a way to limit the Prev / Next to a specific contenttype?

I would like to have only Prev / Next for the contenttype 'post'

[spf13]

This feature doesn't currently exist. We can add it though. Need to figure out the right way to do it so it works for everyone.

[mpas]

Would be great! Thanks for picking this up!

[yacoob]

@mpas, I'm using something like that:

{{ with .Prev }}{{ if eq .Type "post" }}
    <a href='{{ .RelPermalink }}'>...</a>
{{ end }}{{ end }}

That only works if your pages are at the beginning or end of the list.

[chibicode]

👍 I'd appreciate this feature. @yacoob doesn't that approach fail if .Prev isn't of the post type?

[bep]

In 0.13 there is .NextInSection, .PrevInSection.

[chibicode]

@bep totally missed that...thank you!

[chibicode]

It doesn't seem to work unless you're on a section page though. It's returning me nothing on a single post page.

[bep]

It works for what it says it does. Nothing more, nothing less.

[bep]

Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't.

If this is a bug and you can still reproduce this error on the latest release or the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.