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
Describe the bug
When I try to generate the table of contents for a post with the ShowToc: true option, I don't see the TOC on the post as expected.
Device/Os: Manjaro
Type: Desktop
Browser and version: Mozilla Firefox 108.0.1
Hugo Version [ >=0.83.0 expected]: 0.108.0
Theme Version [e.g. v4.0, master, or commit-id ]: d3d90be
Steps to reproduce the behavior:
Create an org file with hugo new post.org with at least one heading (Eg: * Heading )
Add ShowToc: true in the front matter of post.
Serve the site with hugo serve -D.
Open the page and see that the TOC is not visible.
However, note that the TOC is displayed if a .md file was made instead of a .org file.
Expected behavior:
Table of Contents was supposed to appear as expected.
Additional context
Upon debugging, I found that changing the regexp in this line from <h[1-6].*?>(.|\n])+?</h[1-6]> to <h[1-6].*?>(.|\n)+?</h[1-6]> (removed a ] character in the middle) seems to give expected behaviour.
Making this change locally fixed the bug for me, but I do not understand why it happened!
The text was updated successfully, but these errors were encountered:
Describe the bug
When I try to generate the table of contents for a post with the
ShowToc: true
option, I don't see the TOC on the post as expected.Steps to reproduce the behavior:
hugo new post.org
with at least one heading (Eg:* Heading
)ShowToc: true
in the front matter of post.hugo serve -D
.However, note that the TOC is displayed if a
.md
file was made instead of a.org
file.Expected behavior:
Table of Contents was supposed to appear as expected.
Additional context
Upon debugging, I found that changing the regexp in this line from
<h[1-6].*?>(.|\n])+?</h[1-6]>
to<h[1-6].*?>(.|\n)+?</h[1-6]>
(removed a]
character in the middle) seems to give expected behaviour.Making this change locally fixed the bug for me, but I do not understand why it happened!
The text was updated successfully, but these errors were encountered: