Debugging missing content errors

[jackbaty]

First, thanks for continuing work on the theme.

I'm seeing errors when rendering the site which I think are caused by poorly-constructed frontmatter in one or more of my thousands of post files. This isn't surprising, as I've been migrating between blogging platforms for 20 years now.

So here's example output from the render:

ERROR 2020/12/12 08:23:25 render of "page" failed: execute of template failed: template: posts/single.html:92:124: executing "content" at <partial "function/content.html">: error calling partial: "/Users/jbaty/baty.net/themes/codeit/layouts/partials/function/content.html:4:19": execute of template failed: template: partials/function/content.html:4:19: executing "partials/function/content.html" at <partial "function/ruby.html" $content>: error calling partial: partial that returns a value needs a non-zero argument.
ERROR 2020/12/12 08:23:25 render of "page" failed: execute of template failed: template: posts/single.html:96:12: executing "content" at <partial "single/footer.html" .>: error calling partial: "/Users/jbaty/baty.net/themes/codeit/layouts/partials/single/footer.html:54:32": execute of template failed: template: partials/single/footer.html:54:32: executing "partials/single/footer.html" at <partialCached "function/path.html" $value $value>: error calling partialCached: partial that returns a value needs a non-zero argument.
ERROR 2020/12/12 08:23:25 render of "page" failed: execute of template failed: template: posts/single.html:96:12: executing "content" at <partial "single/footer.html" .>: error calling partial: "/Users/jbaty/baty.net/themes/codeit/layouts/partials/single/footer.html:54:32": execute of template failed: template: partials/single/footer.html:54:32: executing "partials/single/footer.html" at <partialCached "function/path.html" $value $value>: error calling partialCached: partial that returns a value needs a non-zero argument.
ERROR 2020/12/12 08:23:25 render of "page" failed: execute of template failed: template: posts/single.html:96:12: executing "content" at <partial "single/footer.html" .>: error calling partial: "/Users/jbaty/baty.net/themes/codeit/layouts/partials/single/footer.html:54:32": execute of template failed: template: partials/single/footer.html:54:32: executing "partials/single/footer.html" at <partialCached "function/path.html" $value $value>: error calling partialCached: partial that returns a value needs a non-zero argument.
Built in 4497 ms
Error: Error building site: failed to render pages: render of "page" failed: execute of template failed: template: posts/single.html:92:124: executing "content" at <partial "function/content.html">: error calling partial: "/Users/jbaty/baty.net/themes/codeit/layouts/partials/function/content.html:4:19": execute of template failed: template: partials/function/content.html:4:19: executing "partials/function/content.html" at <partial "function/ruby.html" $content>: error calling partial: partial that returns a value needs a non-zero argument.

In my fork of the original LoveIt theme, I added conditionals such as {{- if ne "" $content -}} to the problem templates. This prevents the symptom, but doesn't really fix the problem.

So, finally!, my question is: Is there a recommended way to track down which source content files have the offending frontmatter? I'd rather correct that than cheat and work around it in the templates/layouts.

Thanks for any tips you might have.

Jack

[victor-pogor]

Hi @jackbaty.

Sorry for the long response. The discussion feature is on the BETA status and I expected that the number of open discussions will appear in the Discussion tab and, for this reason, I did not see your question.

I will analyze this problem and see what I can do. 🙂

[sosiristseng]

Hello @jackbaty. Please see the relevant issue #68. The reason is that you might have one or more empty posts on your website. New versions of Hugo will refuse to add partial templates to empty content and throw an error. I made a PR #79 to fix this.