-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Duplicate target paths warning after upgrade to v0.115.0 #11187
Comments
This is a side effect of the fix for fa0e16f We will fix this, but to me it does not make sense to have this enabled when running the server, so I suggest you at least temporarily turn it off in your server setup (or config) and just do |
We could reset and rerun it on server rebuilds, but that report needs a full build to make sense. Also clean up the config vs flags in this area: Make all config settings match the flags e.g. `printPathWarnings`, but set up aliases for the old. Fixes gohugoio#11187
We could reset and rerun it on server rebuilds, but that report needs a full build to make sense. Also clean up the config vs flags in this area: Make all config settings match the flags e.g. `printPathWarnings`, but set up aliases for the old. Fixes #11187
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes
After upgrading from v0.114.1 to the latest version, I receive duplicate path warning for every content file every time I change, and save a file.
Steps to reproduce:
curl -sSfL https://github.com/xeptore/blog/archive/main.tar.gz | tar -xzvf -
pnpm
(pnpm install
)make run
layouts/404.html
If you follow the above steps having hugo version 0.114.1, no path warnings will be printed in the terminal. But, if you upgrade the hugo version to v0.115.0, and try step 4, a duplicate target path warning will be printed similar to the following:
The text was updated successfully, but these errors were encountered: