-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Handle uglyURLs ambiguity in Permalink #3102
Comments
The repo you link to does not look like the site you describe (no motorhome). |
sorry, but all the site is in german. I hope this will solve this - I translated the excerpts for the convenience of the readers as the support forum is in english. But translate all of the site - I hope this will not be necessary ... |
I updated the structure above to match the actual repo. Readme.md is also updated. |
OK, I see it now, but I'm not sure how to solve it. Maybe others will. There is an
|
That said, a workaround that should work for you is to put a
|
Thanks - I did not know about that override - will test it. update: and it works, the only thing is: I tested on server and from local storage. Thanks again. |
This is a pretty fundamental change in Hugo, but absolutely needed if we should have any hope of getting "multiple outputs" done. This commit's goal is to say: * Every file target path is created by `createTargetPath`, i.e. one function for all. * That function takes every page and site parameter into account, to avoid fragile string parsing to uglify etc. later on. * The path creation logic has full test coverage. * All permalinks, paginator URLs etc. are then built on top of that same logic. Fixes gohugoio#1252 Fixes gohugoio#2110 Closes gohugoio#2374 Fixes gohugoio#1885 Fixes gohugoio#3102 Fixes gohugoio#3179 Fixes gohugoio#1641 Fixes gohugoio#1989
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. |
Link to repo - this includes the following:
I find this working: create a
/section/index.md
in a section and it renders to/section/index.html
in that same section in the public folder.I like to have an index-file in each content subdirectory as every webserver I know will deliver this when a user uses an address like
http://domain.tld/section/
.All works fine so far.
I use the following structure:
and this renders to
which is ok so far - and as expected following @bep 's definition.
Now I use the following code to produce a sidenav within the womo section.
It ends up like this:
which obviously is wrong since the first line should be like
So at least for creating the menue index.md is NOT treated as content and metadata for a single page.
Hugo uses linktitle from the frontmatter of
/section/index.md
but the created link instead points to/section.html
which gives a simple list but not the content of/section/index.md
.That's why I used to rename
/section/index.md
to something else like/section/intro.md
in the snapshots above and everything worked fineThe text was updated successfully, but these errors were encountered: