Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cascade type files switch to default layout when changed #6538

frank-segui opened this issue Nov 25, 2019 · 1 comment

Cascade type files switch to default layout when changed #6538

frank-segui opened this issue Nov 25, 2019 · 1 comment


Copy link

@frank-segui frank-segui commented Nov 25, 2019

What version of Hugo are you using (hugo version)?

$ hugo version
Hugo Static Site Generator v0.59.1-D5DAB232/extended darwin/amd64 BuildDate: 2019-10-31T15:27:09Z

Does this issue reproduce with the latest release?

Yes. Using extended version.


I am using multiple content folders with cascade.type set. When I make a change in the markdown of one of the files inheriting the type, it switches to the default layout. Then I have to restart hugo for it to pick the the correct layout.

This does not happen for files at the same level of the cascade.type, just for all files on nested folders under the with the cascade.type.

I have a minimal example here:

on hugo serve, changing a file under content/type/dir will change all files in that dir from Another type layout to Default layout.

What I expected

Making a change in a file keeps the layout inherited from its nearest cascade.type.

@bep bep added the Bug label Nov 25, 2019
@bep bep added this to the v0.60 milestone Nov 25, 2019
bep added a commit to bep/hugo that referenced this issue Nov 26, 2019
Copy link

@github-actions github-actions bot commented Feb 12, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

No branches or pull requests

2 participants