Error: failed to resolve output format #2034
-
Describe the bugwhen I cloned the original academic theme, it has Error: from config: failed to resolve output format "WebAppManifest" from site config issue when running hugo but one week ago it was fine. To ReproduceSteps to reproduce the behavior:
Expected behaviorno website can be built Technical details:
require (
If applicable, add screenshots to help explain the issue. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 2 replies
-
Consider upvoting or commenting on the Hugo bug report at gohugoio/hugo#8591 A workaround is documented on the Troubleshooting page: https://wowchemy.com/docs/guide/troubleshooting/#error-failed-to-resolve-output-format |
Beta Was this translation helpful? Give feedback.
-
Hello
I added to the config.tmol in config/_deault/config.toml and now it gives me new error..
content/home/demo.md:76:1": failed to extract shortcode: template for shortcode "callout" not found
Thanks
… On Dec 16, 2020, at 3:54 PM, Geo ***@***.***> wrote:
The following excerpt can be added to your config:
[mediaTypes."application/manifest+json"]
suffixes = ["webmanifest"]
[outputFormats.WebAppManifest]
mediaType = "application/manifest+json"
rel = "manifest"
See https://github.com/wowchemy/starter-academic/blob/dc6940c815055c9c2eaddfe59939d0c76e6f12eb/config/_default/config.toml#L49 <https://github.com/wowchemy/starter-academic/blob/dc6940c815055c9c2eaddfe59939d0c76e6f12eb/config/_default/config.toml#L49>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#2034 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSQA2K4W52U7AAKZVJE2ELSVFCDZANCNFSM4U6YCX5Q>.
|
Beta Was this translation helpful? Give feedback.
-
Thanks! It works! Great that I don’t need to migrate my website again to a new template.
… On Dec 16, 2020, at 4:02 PM, Geo ***@***.***> wrote:
See https://wowchemy.com/docs/faq/#error-file-not-found-or-failed-to-extract <https://wowchemy.com/docs/faq/#error-file-not-found-or-failed-to-extract>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#2034 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSQA2LCVOU7T27WQX5Y5ZLSVFDCHANCNFSM4U6YCX5Q>.
|
Beta Was this translation helpful? Give feedback.
-
This is such a frequent bug, and with every release, and how knows what, it always come back in a new format. I think it would be good to write a bit more about it the documentation, because I do not think that https://wowchemy.com/docs/faq/#error-file-not-found-or-failed-to-extract explains the problema and gives a solution on Windows. Many people use wowchemy with blogdown, which runs hugo with its own parameters, and I do not see how I could emulate the steps you are suggesting. I have sevaral sites running on wowchemy, but I spend more time reinstalling everything that developing them. I tried with a freshly forked wowchemy academic starter page in a freshly installed hugo 0.81.0 now and it just does not work. My sites work on netlify in Ubuntu, but it is impossible to build them locally on Windows 10. |
Beta Was this translation helpful? Give feedback.
-
I got this error today. However, i only corrected a typo. So i thought that it must be related with updated hugo or updated hugo modules. |
Beta Was this translation helpful? Give feedback.
-
Actualizar la variable de entorno HUGO_VERSION funcionó para mí. |
Beta Was this translation helpful? Give feedback.
-
I tried to deploy hugo with wowChemy on Cloudflare and I received that error |
Beta Was this translation helpful? Give feedback.
Consider upvoting or commenting on the Hugo bug report at gohugoio/hugo#8591
A workaround is documented on the Troubleshooting page: https://wowchemy.com/docs/guide/troubleshooting/#error-failed-to-resolve-output-format