seo-metadata.html uses deprecated .Page.IsNode (Hugo 0.163+)
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- hugo
- Domain
- web-dev
Research direction
Open layouts/partials/seo-metadata.html and inspect the canonical-URL logic around the deprecated .IsNode check. Replace that condition with the proposed supported equivalent, then build the site with Hugo v0.166.0 and confirm the deprecation warning is gone while canonical URLs still work.
Written by the indexing model from the issue text.
Description
Context
While reviewing/testing PR #536 (JSON-LD structured data + canonical URLs), building the site with Hugo v0.166.0 emits:
WARN deprecated: .Page.IsNode was deprecated in Hugo v0.163.0 and will be removed in a future release. Use .Page.IsBranch or not .Page.IsPage instead.
The warning comes from layouts/partials/seo-metadata.html, in the canonical-URL logic:
{{ if .IsNode }}
{{ if .Paginator }}
...
{{ end }}
{{ end }}
It's non-blocking today (the site still builds correctly), but Hugo has flagged it for removal in a future release, which would break the build once that happens.
Proposed change
Replace .IsNode with not .IsPage (or .IsBranch, equivalent for this case) so the partial keeps working after Hugo removes the deprecated method.
Note
This is separate from #578 (which pins the Hugo version across environments but explicitly excludes template-deprecation fixes from its scope).
- Dominant language
- JavaScript
- Stars
- 25
- Forks
- 88
- Avg merge
- 53m
- Merged PRs (30d)
- 17
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microcks/microcks.io
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microcks/microcks.io#566 · 5 comments ·
-
component/documentation kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microcks/microcks.io#556 ·
-
automated issue contribution message good first issue help wanted report
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microcks/microcks.io#584 · 7 comments ·
-
component/rendering good first issue kind/task
microcks/microcks.io#578 · 1 comment · 2 assignees ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microcks/microcks.io#564 · 6 comments · 1 reaction ·
All issues in microcks/microcks.io
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100