-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Page.URL is deprecated and will be removed #262
Comments
You should be searching for |
Thank you for your recommendation. This is exactly what I did before asking for help, and this is the output of the command hugo server -D: I just replaced ".URL" by ".Permalink" in the files : Thank you again. |
@cppcms-testing Why are you trying to fix this? It's a warning and should not be breaking your site.
What errors? It's a warning. I run 40+ Hugo sites in production and have not had a problem. It will be fixed before it becomes an error.
Can you explain the harm being done to Hugo? The theme works perfectly and is used by many people. I built the theme on my free time and contribute to Hugo and the community as much as I can. Perhaps we should charge you money for the theme so we can dedicate resources to supporting it? Would you prefer that, or would you prefer to use a free open source theme that you're welcome contribute to. |
After a fresh install of Hugo and the theme "ananke", and after generating a new post with the command:
hugo new posts/my-first-one.md
there is a warning:
Page.URL is deprecated and will be removed in a future release. Use .Permalink or .RelPermalink. If what you want is the front matter URL value, use .Params.url
Every time the command:
hugo server -D
is issued, this warning shows up. I have been looking in vain for the string "Page.URL" . I tried another theme. There is no warning. Everything is working fine.
I really like the Ananke theme and would like to use it as a starting theme.
This is a current warning but the solutions found in various forums do not work for me or screw up everything.
Does the author of this theme can help me correct it. I cannot afford to publish in production something with warning, or worse, with errors.
Thank you for the development of themes and for your help.
The text was updated successfully, but these errors were encountered: