-
Notifications
You must be signed in to change notification settings - Fork 29
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
Code breaks build #17
Comments
The |
I'd happily accept a PR @LaytonLee ! |
Thanks, I think there maybe 3 different ways to fix it:
Personally, I prefer the last 2 solutions. I think it would be better if the theme could set and use a default configuration file, but it's not available currently: gohugoio/hugo#1344. Which approach do you think is preferable? Alternatively, do you think there is a better solution? |
Hello, so i tried using fink-free, i'm absolutely new to hugo and don't know any programming, so i need help with this please. When i run "hugo server -b http://10.10.1.45/blog -D --bind=0.0.0.0" I get this I didn't make another issue because i figured this issue might be related? |
Can you please make sure you're using the latest version of the theme, share the version of You can also try the following: cd themes/ink-free/exampleSite
hugo serve --themesDir ../.. The error in this issue only occurs when your |
Hi, i've migrated to grav, someone told me that .md are limited and i found the workflow of doing a post being kind of a hassle, i have a homelab and i wanted to make a blog with what i do experiments and such. I had the latest one that is avalable on "apt install hugo" and the latest update of ink-free because i git cloned it yesterday. A friend of mine fixed it for me in the end but i moved to something else because of the workflow. ANd btw, not sure if you know, on the blog repo, the deploy thing in the README.md dosen't work, the action is not found. |
https://github.com/chollinger93/ink-free/blob/master/layouts/index.html#L32
That line breaks the build if wpm is not configured. You need to wrap it with
with
orif
unless that is the intended behaviour.The text was updated successfully, but these errors were encountered: