Custom Post Order vs Get Post

This is a simple plugin that enables users to modify the order in which posts are displayed on all pages(or in selected categories) of the blog. This is very useful when you have a blog in which you want to display posts in the order they were posted, from the first post being the oldest one, to the last post which is the most recent one, or the other way around. The options provided with the plugin at this moment allow users to order the displayed posts by post date, post title, post author, last time modified and post slug, either ascending or descending. These post display options can be set by accessing the “Manage->Custom Post Order” link, for wp2.6, and “Tools->Custom Post Order” link, for wp2.7.

Get Post adds a tag that allows you to retrieve and display the latest post identified by a specific set of parameters. When this plugin is active, any post or page can contain the get-post markup as follows: [get-post tag=some-tag] This will be replaced with the latest post tagged with the given tag. Parameters The parameters control which posts are retrieved by get-post. Options can be used in combination to build a list of criteria for post or posts to retrieve. By mixing criteria, you can exert a lot of control over the post(s) which are found by the plugin. [get-post tag=some-tag random show=3] One note on WordPress in general: if you specify criteria that WordPress can’t match, it will make something up. For instance, if you specify a tag or category that doesn’t exist, it will simply retrieve the latest post with no indication that anything is wrong. Take care to ensure that the options you specify are what you intend. Several of these parameters work best when specifying the slugs. For instance, when specifying a tag it’s best to use the slug value rather than the full name of the tag. To find the slug, see the admin panel -> posts -> post tags. The slug is listed right on that page. You may wish to specify an option value with a space in it. This is accomplished with quotes: [get-post option="a value with spaces"] tag: Specify a tag to search for. The tag’s slug should be specified. [get-post tag=some-tag] category: Specify a category to search for. The category’s slug should be specified. [get-post category=some-category] show: Specify the number of posts to show. [get-post show=5] template: Specify the template to use. This specification overrides the template set in the options panel of the admin interface. See the template section for more details on template tags. NOTE: If entering any HTML into this, please be sure to select the HTML editor rather than the visual editor. [get-post template=" Title: {title} "] random: Select a random post from the matching criteria [get-post random] default: This isn’t really an option. By default, get-post displays the latest blog post. [get-post] Templates Get-post ships with a default template that should render the usual post details in a form that fits well with most themes. You can customize this template to add or remove data from the included post. Additionally, you can use the template parameter to the [get-post] tag to specify a one-off template. Using the show parameter will retrieve multiple posts. In this case, the template will be repeated one time for each retrieved post. These tags are replaced with the value from the retrieved post. For instance, a template containing {title} will actually have the title of the retrieved post, rather than the word title. {title}: The title of the post. {content}: The content of the post. {author}: The author of the post. {date}: The date the post was written. {time}: The time the post was written. {permalink}: A link to the post itself. {authorlink}: A link to all posts by the post’s author. {id}: The post’s ID number. Examples Indicate when your blog was last updated: Blog last updated [get-post template="{date} at {time}."] Link to the latest post: Check out my post: [get-post template=" {title} "] How it works This plugin does something a little bit unorthodox: It reenters “The Loop” while the post content is being rendered. Then, it calls whatever WordPress internal functions will safely work, using raw data from $post when these functions are unsafe to call again. People curious about the internals should examine class-get-post-getter.php. The class is structured to be reusable by any other GPL2 projects.