dimitryz

With the Custom Pagination plugin, a user may customize the look of a post’s next and previous links using the HTML editor. It is built by <a href="http://webit.ca" rel="nofollow ugc">WebIT.ca (Dimitry Zolotaryov)</a> and funded by <a href="http://datedaily.com" rel="nofollow ugc">DateDaily.com</a>: an online dating and relationship blog.
The link is created by selecting the text label within a post’s body and clicking the link icon. In the Link URL field, the following values will produce a link to another page:
<ul>
<li>page:next links to the next page</li>
<li>page:prev or page:previous links to the previous page</li>
<li>page:first links to the first page of the post</li>
<li>page:last links to the last page of a post</li>
<li>page:n links to the nth page of a post (e.g. page:2 for the second page)</li>
</ul>
If link is directing to a page that does not exist — for instance page:next on the last page –, the link and the link text do not appear.
All links processed by Custom Pagination will have the added class name ‘page’. If you wish to style such links, in your CSS, add the line:
<pre><code>a.page { /* page style goes here */ }
</code></pre>
For more information, visit the <a href="http://webit.ca/2009/08/custom-pagination-plugin-for-wordpress/" rel="nofollow ugc">Custom Pagination plugin homepage</a>.

Custom Pagination

The Custom Pagination plugin allows a user to insert custom next, previous or numbered page links into a post.

Alley

Matthew Boynes

WordPress has a wonderful editing model with its “draft workflow”, where writers can save unpublished drafts, preview posts, submit drafts for review from a superior, and even schedule a post’s publication. This is all that most writers and teams ever needed for a blog. WordPress has extended beyond blogs, and has grown to be the preferred platform for any person or team writing for the web. While WordPress has evolved, its editing model has not, and this editing model is limited. Once a post is published, edits cannot follow the same workflow. That’s where this plugin comes in. This plugin has two powerful features, the ability to clone posts and the ability to replace posts with another, which combined, allow writers to leverage core’s “draft workflow” for published posts.
<h4>Features</h4>
<ul>
<li>Create clones of existing posts. The replicas are created as drafts, and have all the same data (including terms and post meta) as the original post. The only things not cloned are child posts (which include revisions, attachments, and other posts)</li>
<li>Replace one post with another. The replaced post becomes a revision of itself, the replacing post is essentially deleted, and you’re left with the replacing post’s data with the post ID and slug of the replaced post.</li>
</ul>
Combined, these features give writers a pseudo-“fork and merge” model. Published posts can be cloned, the clones edited as any other draft can be, then the originals replaced with the clones.
Individually, these features are equally as useful. You don’t need to use the “fork and merge” model to take advantage of this plugin.

Clone & Replace

Gives you the ability to clone posts, and replace posts. Together, you have a very powerful tool for a fork/merge editing model.

Custom Pagination vs Clone & Replace