-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
navigation.Page is nil for taxonomy pages (Hugo v0.128.2+) #12652
Comments
See #12638. There's a long story here and I think I introduced this when we got content adapters into the mix, but:
I'm going to close this as "will not fix". I do apologise if I broke something, it was not my intention (or, at least the intention was ... nobel). |
@bep it's perfectly fine, I just didn't expect this coming from a patch release 😅. I would perhaps update the release notes to clearly mention this problem, as I did not find it very clear. Nevertheless, thanks for you continuous work on Hugo! |
Yea, well ... In my head it fixed a breaking bug, which is what patch/bug releases are for. |
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. |
Hi!
Since Hugo 0.128.2, it seems that the menu navigation is not working as it did before. To be specific, the
pageRef
cannot find pages by their output permalink. Here's a bit of myconfig.toml
, where you can see my taxonomies and menu. Note that/articles
and/photos
are categories.Here's the code that fails:
With the following error:
From my tests, it seems that
.Page
is now nil for/articles
and/photos
, where it used to be correctly populated. The workaround is to just change it to/categories/articles
and/categories/photos
. That way didn't work before 0.128.2, but seems to be necessary now.What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes, it is a new issue since 0.128.2. Since commit 8cf96f2 to be exact.
The text was updated successfully, but these errors were encountered: