You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of Hugo are you using (hugo version)?
$ hugo v0.122.0-b9a03bd59d5f71a529acb3e33f995e0ef332b3aa+extended windows/amd64
Tested versions:
Hugo extended windows-amd64 versions 0.123.0 - 0.125.6
Does this issue reproduce with the latest release?
Yes
Bug description
Cascade property affects the next page with similar name.
We use cascade in one of our pages (/team) to prevent rendering its children separately. But the cascade property affects the next following page (/teams).
Renaming the folder "/teams" to "/xteams"
→ "/xteams" was rendered
Put the same cascade properties pages where the next page had an similar name
→ E.g. cascade properties were added to "/microsoft" and the next page ("microsoft-365") wasn't rendered anymore
Conclusion
Cascade should only affect children of an page.
→ /page/...
But cascade affect every page where the name starts with the name of the page with the cascade properties.
→ /page...
The text was updated successfully, but these errors were encountered:
What version of Hugo are you using (
hugo version
)?Tested versions:
Hugo extended windows-amd64 versions 0.123.0 - 0.125.6
Does this issue reproduce with the latest release?
Yes
Bug description
Cascade property affects the next page with similar name.
We use cascade in one of our pages (/team) to prevent rendering its children separately. But the cascade property affects the next following page (/teams).
File setup
/content
├ /de
│├ /...
│├ /team (List of our employees)
││├ /employee_1
│││└ index.md
││├ /...
││└ _index.md
│├ /teams (Articles about Microsoft Teams)
││├ /article_1
│││└ index.md
││├ /...
││└ _index.md
│├ /...
...
Code
/content/de/team/_index.md:
Tests
→ "/xteams" was rendered
→ E.g. cascade properties were added to "/microsoft" and the next page ("microsoft-365") wasn't rendered anymore
Conclusion
Cascade should only affect children of an page.
→ /page/...
But cascade affect every page where the name starts with the name of the page with the cascade properties.
→ /page...
The text was updated successfully, but these errors were encountered: