WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

#5260 closed defect (bug) (invalid)

<!-- nextpage --> Problem

Reported by: ReneeGirl Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.3
Component: General Keywords: <!-- nextpage -->
Focuses: Cc:

Description

In /wp-admin/edit-pages.php, the "more" bbcode should be changed to "nextpage". I spent forever working and reworking my page template trying to figure out what was wrong but found here on the tracker the "nextpage" tag and that fixed my problem. Not a big deal, but if you've not made pages that span multiple pages in WordPress before then it is very vexing.

Change History (8)

comment:1 ReneeGirl6 years ago

  • Type changed from enhancement to defect

comment:2 foolswisdom6 years ago

  • Component changed from Optimization to General
  • Milestone changed from 2.3.1 to 2.4

comment:3 Viper007Bond6 years ago

No, it shouldn't be. They are completely different. For example, I use <!--more Some text here--> all the and I never, ever have used <!--nextpage-->.

I'm all for having both, but don't remove "more". I think it's probably used 100x as much.

comment:4 ReneeGirl6 years ago

So what do you use for the more tag then? <!-- more (What?) --> Just curious. And as far as the rest, I seem to remember the next page tag, unless I'm going senile xx;

comment:5 Viper007Bond6 years ago

It's used for created an auto-except of sorts.

For example:

This part of the post will display on the homepage, archives, etc.

It's a really interesting article. Oh, and hey, here's some big pictures or a ton of text:

<!--more-->

This text will ONLY appear on the single post view.

comment:6 DD326 years ago

Can we get a "Next Page" item in 2.4's Visual editor? Similar to the More button?

comment:7 mtekk6 years ago

This seems to be more of a misunderstanding ticket than an actual bug. For requesting that the <!--nextpage--> tag gets a button there is ticket #6255.

comment:8 lloydbudd6 years ago

  • Milestone 2.5 deleted
  • Resolution set to invalid
  • Status changed from new to closed

mtekk, thank you. I think you're correct. Closing as invalid for now.

Note: See TracTickets for help on using tickets.