You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a post tagged with, say, "Milk" and another tagged with "milk". These are treated as distinct tags within Jekyll, as I see both when iterating through site.tags and my tag list page.
However, no tag page is generated for the capitalized one. That is, the page <site>/tag/milk/index.html is generated, but NOT <site>/tag/Milk/index.html.
Something to do with case sensitivity on the underlying file system? (I'm on a Mac, FWIW).
For my particular usage, I don't need two separate tag pages, I'd be happy to coalesce both of them, preferably without having to edit all the posts.
The text was updated successfully, but these errors were encountered:
Facing this issue from a slightly different angle: I need to display tags with their "pretty" name, but generate pages with a slugged URL (e.g. parameterize) for nicer URLs. This would also prevent the capitalization issue.
This seems like an underlying issue with Jekyll — do you know of any easy way to inject functionality into Jekyll's site.tags and post.tags without monkeypatching the methods? Jekyll doesn't seem to provide a nice injection mechanism =/ or is this something that could/should be handled in a plugin like jekyll-tagging?
I have a post tagged with, say, "Milk" and another tagged with "milk". These are treated as distinct tags within Jekyll, as I see both when iterating through
site.tags
and my tag list page.However, no tag page is generated for the capitalized one. That is, the page
<site>/tag/milk/index.html
is generated, but NOT<site>/tag/Milk/index.html
.Something to do with case sensitivity on the underlying file system? (I'm on a Mac, FWIW).
For my particular usage, I don't need two separate tag pages, I'd be happy to coalesce both of them, preferably without having to edit all the posts.
The text was updated successfully, but these errors were encountered: