Skip to content
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

Only one tag page generated from tags that differ only in capitalization #25

Open
efung opened this issue Aug 29, 2014 · 3 comments
Open

Comments

@efung
Copy link

efung commented Aug 29, 2014

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.

@pattex
Copy link
Owner

pattex commented Sep 3, 2014

You are right, that should be addressed. Thanks.

@nybblr
Copy link

nybblr commented Nov 18, 2014

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?

@nhoizey
Copy link

nhoizey commented Jun 12, 2015

@nybblr URLs are now "slugged": 11eb1f9

There is now one single page, but the tags cloud still shows the upper and lower-case variants, which leads to another issue: #38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants