WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#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)

comment:1 nacin4 years ago

A fix is probably related to #12047.

comment:2 dd324 years ago

  • Keywords dev-feedback added; nextpage home removed

I can see 3 options here:

  1. Use ?page=xxx for the front page instead of <permalink>/xxx/
  2. Reuse /page/xxx/ for Nextpaging instead of Posts paging on front page
  3. 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.

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.

comment:3 dd324 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [13494]) Re-use /page/xx/ for Post Paging on Page_on_front. Few fixes related to paging on front page. Fixes #12391

comment:4 dd324 years ago

(In [14341]) Fix custom WP_Queries when using page_on_front. Props aaroncampbell. See #12391 (Which caused it), Fixes #12047

comment:5 dd324 years ago

(In [14445]) Handle $wp_query->query being a string in r14341. See #12391, #12047. Fixes #13241

Note: See TracTickets for help on using tickets.