Support » Fixing WordPress » Breaking a post into parts: more and nextpage tags

  • Here are two tags which you can insert through the Quicktags menu buttons as you write or edit a post. Or just type the tags in:
    More – this tag adds a <!–-more--> tag to your post, which puts in a “more…â€? link and puts the rest of your post on another page
    Page – this tag adds a <!–-nextpage--> tag to your post, which continues your post on a second page.
    Notice the syntax is different than you might have seen elsewhere: they won’t work if you type <-more-> or <!-more->
    I notice that the page/nextpage tag doesn’t work with my custom permalinks.

Viewing 7 replies - 1 through 7 (of 7 total)
  • I give up – where are these keys on the us standard qwerty keyboard. <!??–more–>

    wrap the text with “code” tags when posting a message with HTML that you want to appear as HTML

    The quicktags described above are:



    Try not to copy&paste what’s found in the OP to this thread. :)

    I think this thread is a nice example of the MySQL bug that causes so much frustration when WP users have to move their blog/DB and they end up with display errors like in the OP.
    In the forum it happened since the “Big Move” in last December.
    Kaf, first I noticed it when in an old post of mine I was mentioning your name with the correct [í] – and it just got messed up after the move.
    Nothing is perfect, I guess. Not even the code that is supposed to be poetry… 🙂

    Keep in mind that *bug* can be managed. I’ve swapped my db out at least a couple dozen times since I’ve been using WordPress (what can I say, I like to play), and the only time I ran into character translation issues is when I’ve forgotten to log into MySQL with the right charset.

    to log into MySQL with the right charset

    For non-techies like myself it would beneficial if you could explain this in more details 🙂
    Thank you!

    Oh-kay, let’s bypass getting into charsets and discuss the actual tool(s) one uses, which is part of the key here.

    Except for minor db queries, tweaking and the like where I use a number of utilities, including a few I’ve written, phpMyAdmin is my primary method for getting at MySQL databases. Among many reasons for this, one is that I can force a language in settings, or have it prompt me to choose one at login. A *complete* phpMyAdmin installation includes many, many language files. My local installation has three just for English! The difference between these is not in the interface, but in the character set that each uses (utf-8, iso-8859-1 and iso-8859-15).

    *Technically* the language option in phpMyAdmin is the localization for the interface, but it also affects character set used on the (db) server for any and all activities during that session. This includes the charset exports are saved in and imports are converted to.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Breaking a post into parts: more and nextpage tags’ is closed to new replies.