#12391 closed defect (bug) (fixed)
nextpage does now work with a static front page
Reported by: | nickmomrik | Owned by: | |
---|---|---|---|
Milestone: | 3.0 | Priority: | normal |
Severity: | normal | Version: | 3.0 |
Component: | General | Keywords: | dev-feedback |
Focuses: | Cc: |
Description
Using <!--nextpage--> with a static front page does not work.
When using custom permalinks, you get a 404. When using the default permalinks, the URL for page 2 is &page=2.
Tested with r13437
Change History (5)
#2
@
15 years ago
- Keywords dev-feedback added; nextpage home removed
I can see 3 options here:
- Use ?page=xxx for the front page instead of <permalink>/xxx/
- Reuse /page/xxx/ for Nextpaging instead of Posts paging on front page
- Use /xxx/ with a few caveouts:
- Could only be used on sites without a numeric as their first token in the permastruct
- Could be used, however,the maximum number of pages would be 1 less than the minimum length of the token, ie. years would max it to 3 digits of pages, Month or Post ID as the first would reduce it to a max of 0 pages working correctly.
- Could only be used on sites without a numeric as their first token in the permastruct
I'm curious as to what everyone else would expect?
I've got all 3 options working locally, Just need to determine which is the winning solution.
Personally, I'd prefer #3, but it's way too fragile. #2 feel like a good compromise, since the rule already exists and isnt in use. #1 is it, if #2 isnt acceptable - But it feels ugly to have to use a query var for it.
Note: See
TracTickets for help on using
tickets.
A fix is probably related to #12047.