I run the newest version of Hugo 0.147.9 and when I have a page folder in my layouts with a single.html in it… the single in the root of the layouts folder will load for my pages (instead of the one in the page folder). This might be a bug. Here is a minimal example: GitHub - jhvanderschee/layoutbu…

The layouts/page construct, where “page” refers to the “page” page kind, is not supported with v0.146.0 or later. This is intentional; not a bug. See this comment from bep.

How would one target the the single of the Kind ‘page’ in the new template layout? I now use this in the page.html: {{ if eq .Type "page" }} ... {{ else }} ... {{ end }} Feels clunky to me. I would rather have a separate file. Another problem with this approach is that is makes it impossib…

[image] jhvanderschee: target the the single of the Kind ‘page’ these will render your contact page layouts/page.single.html ^Kind ^Layout /layouts/page.page.html ^Kind ^Type (= 'page' if not set in front matter) if you have both layouts the firs…

Thank you @irkode ! However… does not seem to work for me. Can you check the code here ? I created a minimal example…

Consider this content structure: content/ ├── posts/ │ ├── _index.md │ ├── post-1.md │ └── post-2.md ├── _index.md └── contact.md To create a unique template for the contact page I would do one of these… Option 1 – Target the logical path (preferred) layouts/ ├── contact/ │ └── page.html …

Sorry… I think I wanted to have a specific layout for all ‘singles’ with .Type = page (no parent folder). Is that possible? I was mixing up .Type and .Kind. Sorry for the confusion.

[image] jhvanderschee: I wanted to have a specific layout for all ‘singles’ Out of curiousity, why? Typically an “about” page and a “contact” page would use different layouts. content/ ├── posts/ │ ├── _index.md │ ├── post-1.md │ └── post-2.md ├── _index.md ├── about.md └── contact.md

True… but sometimes they do not. The most common usecase is that you want all sections to have no single… and only publish singles for the .Type page.

[image] jhvanderschee: you want all sections to have no single… and only publish singles for the .Type page I don’t understand this. Can you please clarify, perhaps with a structural example?

I had this (prior to v0.146.0): layouts/ ├── _defaults/ │ └── single.html (was empty so section singles would not be published) ├── page │ └── single.html (was not empty, but had a nice page layout) How do I do this in post v0.146.0? I prefer to use only 2 files.

[image] jhvanderschee: was empty so section singles would not be published This is an anti-pattern. I still don’t understand this, sorry. Perhaps you can provide an example repo? The example in your initial post doesn’t seem to match the use case you describe… which is a bit unusual.

Possible bug: Single layout for pages in v0.147.9

support

jhvanderschee July 2, 2025, 12:18pm 24

Thank you. Here is a (first) support ticket for this topic: Landing page redered as expected, post itself isn't - #4 by jhvanderschee

Topic		Replies	Views
How to defined custom layout after v0.146.0 support	6	213	May 22, 2025
Documentation of the new template system in Hugo v0.146.0 Announcements	13	637	May 29, 2025
Site builds become unreproducible when using layouts/page folder support	4	103	August 16, 2025
Custom layout not working for contact.md support layouts	10	169	July 27, 2025
Best way to adapt to new template system when using Page.Type support theme-building , layouts	11	129	February 24, 2026

Possible bug: Single layout for pages in v0.147.9

Related topics