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
This issue is not a question, feature request, or anything other than a bug report directly related to Hugo Blox Builder. Please post those things on Discord: https://discord.gg/z8wNYzb
Description
When using a hugo version >= v0.123.0, a book site does not show a TOC anymore on the left side
This issue is stale because it has not had any recent activity. The resources of the project maintainers are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the main branch, consider contributing a Pull Request with a fix.
If this is a feature request, and you feel that it is still relevant and valuable, consider contributing a Pull Request for review.
This issue will automatically close soon if no further activity occurs. Thank you for your contributions.
Preliminary Checks
Description
When using a hugo version >= v0.123.0, a book site does not show a TOC anymore on the left side
Reproduction Link
https://github.com/dlehmenk/blox-book-bug
Steps to Reproduce
Expected Result
There should be a TOC like with version 122 and before
Actual Result
No toc there
What Hugo Module versions does your site use?
module github.com/wowchemy/starter-hugo-research-group
go 1.15
require (
github.com/HugoBlox/hugo-blox-builder/modules/blox-bootstrap/v5 v5.9.8-0.20240513193311-41bd113535e8
github.com/HugoBlox/hugo-blox-builder/modules/blox-plugin-decap-cms v0.1.2-0.20231108143325-448ed0e3bd2b
github.com/HugoBlox/hugo-blox-builder/modules/blox-plugin-netlify v1.1.2-0.20240509231741-c3d23d929bc6
)
What operating system(s) are you seeing the problem on?
Linux
What browser(s) are you seeing the problem on?
Chrome, Firefox
Which Hugo Blox template are you using?
Research Group
What version of Hugo are you using?
Hugo Extended 0.125.7
The text was updated successfully, but these errors were encountered: