Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upDEFAULT_ORPHANS inconsistent with documentation #1568
Comments
This comment has been minimized.
This comment has been minimized.
leotrs
commented
Aug 1, 2016
|
@kernc can you still replicate this? |
This comment has been minimized.
This comment has been minimized.
|
Seems so. With pelican git, given three articles in a paginated category,
results in two pages (1+2). Expected are three pages (1+1+1). Likewise,
results in a single, unpaginated page. Expected are two pages (2+1). Both of these behaviors are inconsistent with docs for Setting in both above cases |
This comment has been minimized.
This comment has been minimized.
leotrs
commented
Aug 14, 2016
|
Sounds like a change in documentation could solve this issue. PRs are welcome. |
kernc
added a commit
to kernc/pelican
that referenced
this issue
Aug 14, 2016
kernc
referenced this issue
Aug 14, 2016
Closed
Fix edge condition with DEFAULT_PAGINATION and DEFAULT_ORPHANS #1992
This comment has been minimized.
This comment has been minimized.
|
That would be the easy and probably invalid fix. Got something better in #1992, I hope. |
This comment has been minimized.
This comment has been minimized.
|
Resolution: invalid #1992 (comment). |
kernc commentedDec 26, 2014
The documentation for
DEFAULT_ORPHANSsetting says:However, with
and with three articles paginated, one appears on the first page and two on the second. The same setup with
DEFAULT_PAGINATION = 2produces a single, unpaginated page.So it seems that
(DEFAULT_ORPHANS + 1)is the minimum number of articles allowed on the last page.