With v0.121.2:
| EN
-------------------+-----
Pages | 8
Paginator pages | 0
Non-page files | 0
Static files | 1
Processed images | 0
Aliases | 0
Sitemaps | 1
Cleaned | 0
With PR #11830:
| EN
-------------------+-----
Pages | 10
Paginator pages | 0
Non-page files | 0
Static files | 0
Processed images | 0
Aliases | 0
Cleaned | 0
On a few occassions I was not able to kill the server with Ctrl+C on the first try, and after several times it stopped with this message:
Error: context deadline exceeded
I've a resources.GetRemote call that's currently returning a bad request (400) error, and at the moment that is expected (the provider site is having issues). I expected the hugo server to terminate after throwing the error, but I have to Ctrl+C to stop the server. With v0.121.2 the server terminates immediately. This is an intermittent problem, and I have not been able to create a mimimal failing example yet.
I see where you're coming from, but
Believe me, I have thought long and hard about this, and I think the current behaviour strikes a sensible balance.
/mysection/mypost
is a canonical content path (so to speak)/mysection/mypost.md
and/mysection/mypost/index.md
can be converted into canonical paths, but they also indicate a filename.I have pushed an update that makes my portable links repo (link portability between Hugo<->GitHub) work again:
https://github.com/bep/portable-hugo-links
I had totally forgot about that repo, and I had no breaking tests ... Now we have tests. And the module mapping from that repo illustrates the the "a filepath is not always what you think it is" problem:
Thanks for the test reports, much appareciated. I will look into them now.