Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix warnings #65

Closed
StefMa opened this issue Jul 24, 2019 · 4 comments · Fixed by #78
Closed

Fix warnings #65

StefMa opened this issue Jul 24, 2019 · 4 comments · Fixed by #78

Comments

@StefMa
Copy link
Owner

StefMa commented Jul 24, 2019

I get the following warnings when I build the site:

Building sites … 
WARN 2019/07/24 10:37:50 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/07/24 10:37:50 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/07/24 10:37:50 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/07/24 10:37:50 Page's .Dir is deprecated and will be removed in a future release. Use .File.Dir.
WARN 2019/07/24 10:37:50 Page's .URL is deprecated and will be removed in a future release. Use .Permalink or .RelPermalink. If what you want is the front matter URL value, use .Params.url.

(See also #61)
We should fix the warnings

@nathanbiller
Copy link
Contributor

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.

@StefMa
Copy link
Owner Author

StefMa commented Oct 2, 2019

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 :)

@Allen616
Copy link

Allen616 commented Nov 8, 2019

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.

@Allen616
Copy link

Allen616 commented Nov 12, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants