Make WordPress Core

Opened 18 years ago

Closed 18 years ago

Last modified 18 years ago

#6184 closed defect (bug) (fixed)

nextpage tag doens't work on front page

Reported by: mnogueir's profile mnogueir Owned by:
Milestone: 2.5 Priority: normal
Severity: normal Version: 2.3.3
Component: General Keywords: nextpage, front page
Focuses: Cc:

Description

Hello there!

I've configured my blog as a CMS, using one static page as my front page. In this page (id=6, for example) i inserted the <!--nextpage--> tag. However, the link created is wrong:

  1. The URL is the blog's home, not the page URL.
  2. There's no trailing slash.

So, i get something like www.domain.com?page=2, which obviously doesn't work. Even if the trailing slash was added, www.domain.com/?page=2 wouldn't work (tried it). Either the front page parses the "page=2" or the created URL must point to www.domain.com/page_id=6&page=2

Am I getting something wrong? Can you reproduce this?

Thanks

Change History (8)

#1 @mnogueir
18 years ago

  • Version set to 2.3.3

#2 @mnogueir
18 years ago

  • Cc mnogueir@… added

#3 @mnogueir
18 years ago

  • Keywords nextpage front page added

#4 follow-up: @mtekk
18 years ago

  • Version changed from 2.3.3 to 2.5

It looks like in 2.5 it works, I'm using the SVN version from Monday the 17th. I've checked it with a permalink structure of /archives/%category%/%postname%/ and the default permalink structure that you experienced the problem in. In both it works flawlessly. Now only if there was an "insert next page tag" as we do have an "insert more tag" button.

#5 @mnogueir
18 years ago

Well, as soon as 2.5 gets "officaly" released I'll update and try it again... Thanks for testing!

#6 in reply to: ↑ 4 ; follow-up: @lloydbudd
18 years ago

  • Milestone changed from 2.6 to 2.5
  • Resolution set to fixed
  • Status changed from new to closed
  • Version changed from 2.5 to 2.3.3

Replying to mtekk:

It looks like in 2.5 it works

Closing as fixed. Thanks mtekk! Please test in 2.5 and reopen if still the same symptom.

PS. mtekk, the version is the latest version you experienced the bug in, so it doesn't seem to be correct to update it to 2.5 .

#7 @mnogueir
18 years ago

OK, Thanks!

#8 in reply to: ↑ 6 @mtekk
18 years ago

Replying to lloydbudd:

PS. mtekk, the version is the latest version you experienced the bug in, so it doesn't seem to be correct to update it to 2.5 .

Yeah, stupid me, I forgot to fully read the nice Reporting Bugs page in the codex.

Note: See TracTickets for help on using tickets.