-
Notifications
You must be signed in to change notification settings - Fork 911
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
After migrating to Hugo module, can no longer load FontAwesome files #1285
Comments
Done some further testing, and it looks like it is an issue with the v0.5.0 release. Trying 0.2.0, 0.3.0, and 0.4.0 all load correctly, upgrading to 0.5.0 and the fontawesome files are no longer loading. Checking the output of hugo it seems there are ~15 static files that are not correctly processed 0.4.0
0.5.0
|
This is a know issue that was raised in #1281 already. It was addressed with PR #1282 (merged) and PR #1284 (not merged yet). Even without #1284 in place, you might be able to work around this. Can you try to update your module to HEAD of main:
Does this cure your problem? |
Thanks @deining. I tried searching for |
@deining Tried that, and it looks to be working. The number of static files is still lower than in 0.4.0, but higher than with 0.5.0
|
I have followed the guide on the Docsy site (https://www.docsy.dev/docs/updating/convert-site-to-module/) to switch from a git submodule to a Hugo module, and most things seem to be working, but now I get a 404 when attempting to load any of the FontAwesome files. Checking the
mod graph
and it looks correct to meThe page is just a generic 404 page when attempting to view the file
I have commented out the
theme
line inconfig.toml
and added themodule
information inI think the only major difference is that I'm running Hugo locally via a docker-compose file. Not sure if there is a change there that's needed.
The text was updated successfully, but these errors were encountered: