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

Change in behaviour for page resources since v0.56 #6208

Closed
stp-ip opened this issue Aug 14, 2019 · 1 comment · Fixed by #6239

Comments

@stp-ip
Copy link

commented Aug 14, 2019

We are using Resources.ByType to aggregate all content files within subdirectories making up a site. This way splitting of content files is enabling a page being made up of various fragments.
Fragments located in [page]/[subdirectory]/index.md don't work since Hugo 0.56 doesn't recognize [subdirectory]/index.md as page resources anymore. Same for 0.57.
Current workaround is to create the fragment as [page]/fragment.md in addition to [subdirectory].
Basically moving index.md to ../fragment.md. That way it is recognized and the theme still works.

This feels like a regression. If this was a misusage, happy to get this documented and fixed on our side.

Specifically this came up with the Syna Theme.
This is also breaking the demo: https://themes.gohugo.io//theme/syna/fragments/faq/

@bep bep modified the milestones: v0.58, v0.57.1, v0.57.2, v0.57.3 Aug 14, 2019

@bep

This comment has been minimized.

Copy link
Member

commented Aug 17, 2019

It would be simpler if you could just point to a content directory showing this problem. I assume this is one example?:

https://github.com/okkur/syna/tree/master/exampleSite/content/fragments/faq

@bep bep added Bug and removed NeedsInvestigation labels Aug 17, 2019

bep added a commit to bep/hugo that referenced this issue Aug 17, 2019

@bep bep closed this in #6239 Aug 17, 2019

bep added a commit that referenced this issue Aug 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.