-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Hugo >0.123.5 failing to render most of website menu #12218
Comments
@danburd I am unable to reproduce this as described. Using Hugo v0.123.8, here's what I did:
Here's what I got: Please provide a failing example. |
Update: the issue is only with headless branch bundles not showing up on the menu. (All of my page bundles were headless, which is why the issue seemed more broad at the time.) That's why the exampleSite worked and mine did not. I don't know if this is an issue with the theme or an issue with Hugo. |
I am not comfortable troubleshooting this without access to your project repository. If you are making your bundles "headless" by adding |
I suppose the correct way to do this is to replace
Thanks. Closing. |
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. |
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes
Hugo 0.123.6, 0.123.7, and 0.123.8 is failing to render most of the website menu in the Book theme where 0.123.5 is doing so without issues. Specifically, it's unable to render the pages which exist in a hierarchy of sections - links to pages that are in the menu's root render successfully. I believe that the operative code to render the hierarchical menu is here, between lines 10 and 25. Sorry that I'm not more knowledgeable about which functions in particular are not working.
I've filed an issue with the theme, but I suspect the issue is with Hugo itself as I don't believe that breaking changes are purposefully introduced in bugfix releases.
The text was updated successfully, but these errors were encountered: