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
Replace deprecated .Hugo with hugo. #171
Conversation
When you request /tags/foo, the web server will redirect you to /tags/foo/ so the browser needs to make two requests. Add the trailing slash in the link so that only one request is needed.
Co-Authored-By: tobinjt <johntobin@johntobin.ie>
Co-Authored-By: tobinjt <johntobin@johntobin.ie>
…into changes-for-upstream
Hugo 0.55 deprecates .Hugo and produces this warning: "Page's .Hugo is deprecated and will be removed in a future release. Use the global hugo function."
I don't understand why the tests are failing :( Thanks, |
I think the problem is the Hugo version used to build the deploy preview. You can change it in the |
…duced because it is not documented.
…duced because it is not documented.
…duced because it is not documented.
…duced because it is not documented.
…duced because it is not documented.
Thanks for the info! There's another deprecation warning: |
There is no problem if we need to bump the minimal version of this theme. It is good to keep things up-to-date. Thank you for the PR and for pointing the deprecation warning. I will create a Issue to remember to fix this problem later. |
Prerequisites
Put an
x
into the box(es) that apply:Potentially, I don't know for sure.
Description
Hugo 0.55 deprecates
.Hugo
and produces this warning:Page's .Hugo is deprecated and will be removed in a future release. Use the global hugo function.
Update the theme to use
hugo
rather than.Hugo
.I marked this as potentially introducing a breaking change because I don't know how backwards compatible this change is.