#5 Solve a problem with URL reference of category

[brunojdo]

Solve a little problem commented in the issue #5 about the missmatch reference between 127.0.0.1 and the real DNS URL.

[GreatEmerald]

I'm surprised this could cause any issues. Technically shere should be no difference between one slash and two slashes (aside from visually looking a bit iffy). What browser are you using?

[brunojdo]

Hi @GreatEmerald I'm using Chrome. In _config.yml add the url: xxxx.github.io and do this test.

This is also was strange to me, but with two slashes this problem happens. I'm testing in Firefox and the problem persists too.

[brunojdo]

I just found another problem in this page, the categories buttons are pointing to {{ site.url }}. I changed to baseurl and works fine.

Current: <a href="{{ site.url }}/category/{{ c_slug }}" class="btn btn-sm btn-default btn-raised">{{ c_slug }}</a>

Change: <a href="{{ site.baseurl }}/category/{{ c_slug }}" class="btn btn-sm btn-default btn-raised">{{ c_slug }}</a>

Can I do this PR too?

Best regards,

[GreatEmerald]

Why would you want to define url, instead of using baseurl in your config? In general it should all be site.baseurl and not site.url in the code too.
And in your suggestion, you are also using an extra slash after {{ site.baseurl }} there, which would create double slashes if baseurl is defined with a trailing slash (which I'm not sure about: is it normally required by Jekyll to define it with one?).

[brunojdo]

I see in many Jekyll templates that url is define with the DNS of the web page, and baseurl is the root of the site that, in general, is empty. But you could define as a /blog for example. I may be wrong, however, It was how I understood the usage of baseurl and url.

[brunojdo]

Another solution is just remove {{ site.url }} from the a href

[GreatEmerald]

Hm, right, I do have both defined on my site as well (with a baseurl of /jekyll without a trailing slash). So is it post.url that has a leading slash in it, then?

And no, you need to have {{ site.baseurl }} in there, else baseurl support gets broken.

I suppose you can add the second change to this PR as well, then.

[brunojdo]

Ouky douky! 👍

[codeasashu]

Thanks for the PR