Closed pierreprinetti closed 6 months ago
Something interesting happens when I set a base URL.
$ HUGO_BASEURL=https://example.com/ hugo --minify
Start building sites …
hugo v0.123.6+extended linux/amd64 BuildDate=unknown
| EN
-------------------+-----
Pages | 11
Paginator pages | 0
Non-page files | 0
Static files | 0
Processed images | 0
Aliases | 2
Cleaned | 0
Total in 41 ms
First of all, it succeeds. And the breadcrumb JSON items now have the correct "position" numbers:
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Posts",
"item": "https://example.com/posts/"
},
{
"@type": "ListItem",
"position": 2,
"name": "This is a reproducer for a PaperMod bug",
"item": "https://example.com/posts/2024-02-27_reproducer/"
}
]
}
(it was minified in the file; I have pretty-printed it here for readability)
Yes you are supposed to use a baseURL and not build with a /
in baseURL, not recommended
Yes you are supposed to use a baseURL and not build with a
/
in baseURL, not recommended
Do I understand correctly that not setting a baseURL is not a valid use-case with PaperMod?
Yes you are supposed to use a baseURL and not build with a
/
in baseURL, not recommendedDo I understand correctly that not setting a baseURL is not a valid use-case with PaperMod?
It's not only about use cases but what implementation works with the rest of the functions without breaking anything.
Describe the bug I am getting this error when running
hugo --minify
:and indeed the tempfile has a scheme.org JSON array with two elements and no comma between them:
I am not sure what triggers the error. Anyway, I could build a reproducer (see below).
Steps to reproduce the behavior:
Expected behavior: I expected the site to build, just like it does when no
--minify
is passed.Repo/Source where this issue can be reproduced: