-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Prevent panic when creating new content if also created by content adapter #12504
Labels
Milestone
Comments
|
Understood. I have added a "page collisions" section to the documentation: |
jmooring
changed the title
Miscellaneous improvements to content adapters
Prevent panic when creating new content if also created by content adapter
May 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These are all minor, and should probably be separated into individual issues at some point, but for now...
1) If a content adapter creates p1, attempting to create p1.md with
hugo new
causes a panic.2) If p1.md exists, and a content adapter creates p1, the content adapter wins. It seems to me it should be the other way around; p1.md should override the content adapter. For example, a module provides content, and you need to override one of the pages provided by the module.See comments below.3) If p1.md exists, and a content adapter creates p1, theSee comments below.--printPathWarnings
flag does not report a page collision.The text was updated successfully, but these errors were encountered: