-
Notifications
You must be signed in to change notification settings - Fork 87
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
previous_page_path includes index.html #15
Comments
My only concern here is that not everyone will want this. |
The way I see it, the following options are consistent:
I don't know why anyone would want to have a mix between the two. Also, |
Yeah the consistency makes sense for sure. The 301 may not be Jekyll. What permalink style do you have set in your config.yml? Maybe we need to default to /base/page:num/ |
I was using There is nginx keyword in the 301 response-body, anyway 301 is the right thing in this case. I just realized someone might have set |
Yeah, we can update the docs. Would you mind submitting a PR? The docs are in
I don't think anyone does this, but we can't be sure. |
Submitted: jekyll/jekyll#3091 Concerning the http://www.paulwrankin.com/blog/2014/10/16/better-jekyll-pagination/ |
This is fixed for Jekyll > 3.0 |
Moved from jekyll/jekyll#3073
paginator.previous_page_path
generatesbase/page2
when on the third page, but for the second page the result isbase/index.html
which is not pretty. Shouldn'tprevious_page_path
generate justbase/
in this case?Here is a sample fix: rovrov@088fd18
base
instead ofbase/
(i.e.chomp("/index.html")
) might be even more consistent if it always works without the trailing slash.The text was updated successfully, but these errors were encountered: