Fix warnings about hugo-fresh HOT 4 CLOSED

I have a branch where I've fixed this, but it's a few commits ahead of other code that I submitted so I'm planning on waiting to submit a PR until my other PRs have been merged.

from hugo-fresh.

That cool. Thank you.
Are you aware of cherry-picks?

If its possible with your changes you could create a new branch and cherry-pick your commits into the new branch and create a PR :)

from hugo-fresh.

I see this is closed but I am still getting similar errors.

WARN 2019/11/07 15:00:29 found no layout file for "HTML" for "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination. WARN 2019/11/07 15:00:29 found no layout file for "HTML" for "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination. WARN 2019/11/07 15:00:29 found no layout file for "HTML" for "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination. WARN 2019/11/07 15:00:29 found no layout file for "HTML" for "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination. WARN 2019/11/07 15:00:29 found no layout file for "HTML" for "section": You should create a template file which matches Hugo Layouts Lookup Rules for this combination. WARN 2019/11/07 15:00:29 found no layout file for "HTML" for "taxonomyTerm": You should create a template file which matches Hugo Layouts Lookup Rules for this combination. WARN 2019/11/07 15:00:29 found no layout file for "HTML" for "taxonomyTerm": You should create a template file which matches Hugo Layouts Lookup Rules for this combination. WARN 2019/11/07 15:00:29 found no layout file for "HTML" for "section": You should create a template file which matches Hugo Layouts Lookup Rules for this combination. WARN 2019/11/07 15:00:29 found no layout file for "HTML" for "section": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.

from hugo-fresh.

I was able to overcome the errors by changing the "disable warnings" format in my config.yaml.

This is the format that corrected the warnings:

disableKinds: ["page", "section", "taxonomy", "taxonomyTerm"]

Following is the existing format in the config.yaml, which still created errors :

disableKinds: -taxonomy -taxonomyTerm

I hope this helps others.

from hugo-fresh.