"Pager 2" weirdness

support
1

I am not sure whether this weirdness is caused by hugo or by the stack theme, so I am going to ask in both places.

I have placed hugo’s destination directory in a github repository so that each time I make changes I can preview them locally, and then push to github, from which neltify picks it up and publishes it.

As I make changes to my blog content and/or theme files, I pay attention to the corresponding modifications made by hugo on the output files, as shown by git.

I have noticed that sometimes, the text "Pager 2 - " is unexpectedly inserted in the following places:

<link rel="stylesheet" href="/scss/style.min.[...].css"><meta property='og:title' content="Pager 2 - Michael's Blog">

and

<meta name="twitter:title" content="Pager 2 - Michael's Blog">

This is happening on pages where it should definitely not be happening, for example on the page with

<title>Pager 10 - Michael&#39;s Blog</title>

Furthermore, if I make a tiny modification to my blog content, and the hugo server rebuilds my blog into the destination directory, and git shows me the new changes, the text “Pager 2” is gone. It will re-appear if I restart the hugo server, and it will disappear again if I make another change.

This is driving me nuts.

Now, try this:

Do a web search for "Pager 2" hugo, and you will get:

  • a couple of results from gohugo.io
  • one result from someone’s blog who talks about hugo pagination, and then…
  • a bunch of results from random blogs out there that are all using the stack theme.

Now, all these pages out there happen to be 2nd pagination pages, so the text “Pager 2” in their title is to be expected. However, what this is telling me is that the stack theme is unique in using text “Pager 2”, so the appearance of that text in unexpected places might be the theme’s fault.

My destination files are here: GitHub - mikenakis/michael.gr-hugo-publish: My blog

My source hugo files (minus the content markdown files) are here: GitHub - mikenakis/michael.gr-hugo-files

My content markdown files are part of my digital garden and therefore not public.

So, as it stands I cannot provide a full working set of source files for reproducing this issue.

I am posting this in case anyone can figure out what is wrong either from the description of the problem, or by looking at the destination files.

2

Same question in the discussions of the theme:

3

I suggest you create some dummy content, and make sure you can reproduce the problem. Then you will be able to “provide a full working set of source files for reproducing this issue.”