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 1.8 breaks header.html partial menu logic #18
Comments
Thank you for your report. |
I confirmed this problem. Hugo changed its behavior at v0.18 https://github.com/spf13/hugo/releases/tag/v0.18 Here they say:
And the document on gohugo.io says now:
So it seems that we have to change all variables in config.toml into lowercase. |
This seems like a bug in Hugo, doesn't it? The conflicting information and
results is confusing, at least.
|
Oh, I misunderstood one thing. And we can access by So we don't need to change config variables into lowercase. Just do above. Thanks, |
I opened a topic in Hugo's discussion forum: https://discuss.gohugo.io/t/config-params-should-be-all-lowercase-or-not/5051/1 to ask a recommended way to solve this problem just in case. |
I guess we found a bug in Hugo together! Thanks for doing the research and posting on the discussion forum. |
Upstream issue: gohugoio/hugo#2907. |
Fix #18 / .Site.Params "fooBar" is not accessible for Hugo v0.18
Everything worked perfectly with Hugo versions <= 1.7, but the menu does not populate anymore.
Everything from hugo-theme-bootie-docs/layouts/partials/header.html line 36 to line 52 appears to now be broken under Hugo 1.8.
My theme is similar enough and experiences this problem, too. In my site's config.toml, I have defined
noCategoryLink
and have amainMenu
array, yet now I get only a 'Home' and a 'Categories' link in the menu. (I want all of the pages defined in theparams.mainMenu
to show up and I don't wantCategories
.)If you build your site with the latest version of Hugo, you should also experience this
I'm not sure which change in Hugo 1.8 (changelog) caused this problem, but I'd be happy to work on this with you.
The text was updated successfully, but these errors were encountered: