I converted my content and I noticed on the home page “Blog” links to itself (https://domain.com/folder) so the “content” pane remains empty when I click on “Blog”.
Why doesn’t it link to https://domain.com/folder/_posts to show a list of posts? Or is something else wrong?
$ cat config.toml
BaseURL = "https://domain.com/folder"
languageCode = "en-us"
theme = "hyde-x"
$ hugo version
Hugo Static Site Generator v0.14 BuildDate: 2015-05-25T18:29:16-07:00
My temp workaround was to change public/index.html to add _posts to the blog link.
Not sure what yo mean by “links to itself” – all the links are in the templates and all up to you (Hugo helps out with some helper methods etc., but do not confuse BaseURL with a link).
By that I mean it links to the “home page”, i.e. my BaseURL folder is domain.com/folder and the Blog (“Posts”) link on the home page domain.com/folder/index.html links to domain.com/folder/index.html (itself).
So when I click on it, it doesn’t do anything. I manually modified domain.com/folder/index.html to link to domain.com/folder/_posts/, so now when I click on the “Blog” link on home page, the right hand pane shows blog posts.
I think it may be a problem with the theme. I’ll try another theme to see if I get the same result.
Edit: okay, I tried with hugo-uno and with that “Blog” links to #blog which instead of taking me (I expect) to domain.com/folder/#blog, it directs me to domain.com (Error 404).
If I manually paste domain.com/folder#blog to navigation bar in the browser, that does expose blog archive in the right hand pane.
Maybe it’s something about Google Drive because it’s URLs aren’t fixed (e.g. www.googledrive.com/host redirects to garbage-www.googledrive.com/host and so on). But I don’t understand why these links aren’t relative to BaseURL, wouldn’t that cause fewer problems? For example, in hugo-uno:
I tried cannonical URLs, with that “Blog” exposes the right hand pane, but then “Archive” links to domain.com/folder/post which leads to 404. I’m (temporarily) giving up!
I found that different themes have different bugs (and more than one - I should have expected that, but…), so troubleshooting by changing something in your config file and trying a different theme at the same time may produce unexpected outcomes