Hugo 0.18 broke my site; now gives "LinkResolver: No page found for xxx" and 404 errors

[richb-hanover]

My site is a straightforward collection of Markdown pages that worked fine for Hugo 0.16.

Regrettably, our hosting provider has switched to Hugo 0.18, and many (perhaps all) relative links between pages in the Markdown now give message of LinkResolver: No page found for xxx

As stated in #2506, setting sourceRelativeLinks: false gets rid of those errors. But...

• Links to files with file suffixes give 404 errors in the browser (but not at compile time with hugo serve, e.g., [Test](/bloat/wiki/Tests_for_Bloat.md)
• Links with a closing "/" (and no suffix) work fine -e.g., [Test](/bloat/wiki/Tests_for_Bloat/)

My question: Is there a way to make the source files work properly again, without editing off the ".md" for my entire site? Many thanks.

PS #1: This is an update of #2891 The Git repo there can be cloned to demonstrate the problem.

PS #2: Here's my config.yaml file:

baseurl: "https://www.bufferbloat.net/projects/"
languageCode: "en-us"
title: "Bufferbloat.net"
disable404: false
canonifyURLs: true
relativeURLs: false

pluralizeListTitles: false
metadataFormat: yaml
params:
  stylesheets: [ "bootstrap.css", "font-awesome.css", "custom.css" ]
  recentTypes: [ "news", "wiki" ]
author:
  name: The Bufferbloat community
  email: bloat@lists.bufferbloat.net
blackfriday:
  plainIDAnchors: true
  sourceRelativeLinks: false

[richb-hanover]

@bep I don't think that this answers the question I asked:

Is there a way to make the source files work properly again, without editing off the ".md" for my entire site?

Many thanks.

[bep]

If you want to ask Hugo-related questions, please use https://discuss.gohugo.io/

[richb-hanover]

@bep I do plan to ask on the forum. However, please forgive me, but I believe there is a bug here somewhere.

My site (containing thousands of files) worked as expected in Hugo 0.16. It does not work in 0.18.

The documentation (at http://gohugo.io/overview/configuration/#configure-blackfriday-rendering) clearly specifies the sourceRelativeLinksEval and sourceRelativeLinksProjectFolder directives may be used.

If sourceRelativeLinksEval is now deprecated, I would wonder also about sourceRelativeLinksProjectFolder, and whether the documentation will be updated to reflect this.

[bep]

Of course, there is a bug or two here, but as no one has shown any interest in solving it / maintaining this feature -- it is much better to remove it than to make people think it's working. And removing the feature does fix the bug.

This feature was contributed by someone from Docker; they have since then stopped using Hugo, and has abandoned their code.

Please take any further questions on the forum.