Troubleshooting of Wowchemy/Hugo

Adding Comments to Website

Local Errors

When I tried to revisit this page a few days later, I encountered an error but I did not change anything since my last edit. So I am adding the troubleshooting section here for my future reference.

Error: failed to resolve output format

https://wowchemy.com/docs/hugo-tutorials/troubleshooting

Users report a commonly occurring Hugo issue with the integrity of the modules cache. Consider upvoting and commenting on the issue to show the Hugo team that you are also affected.

To resolve this Hugo issue, either:

(A) Manually delete Hugo’s default cache folder and re-run Hugo. Hugo’s cache folder defaults to $TMPDIR/hugo_cache/ on Mac/Linux and %TMP%\hugo_cache\ on Windows.

Or, (B) Set a custom Hugo cache folder when you run Hugo, for example: hugo server –cacheDir ./cache/ where ./cache/ is the path of a temporary folder to create. Then you can easily locate and delete Hugo’s cache folder should you experience this issue.

Note: usually hugo mod clean –all should delete Hugo’s cache, however, users report a Hugo bug running the command in this situation. You can provide your feedback on the Hugo issues.

Failed to resolve output

When I tried to launch the server through either hugo or blogdown, it says Error: from config: failed to resolve output format “WebAppManifest” from site config. I found the solution here. However I could not find any temp directory. Here is my solution:

Temporarily remove the “WebAppManifest”, “redirects”, “headers” output types from your config.yaml under the config folder (not the root folder) and run the following commands through Windows PowerShell: hugo mod clean and hugo mod tidy Check that hugo now runs OK with hugo server or blogdown and then add the output types back into your config.yaml.