Get Post vs W4 Post List

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.

W4 Post List builds the lists that WordPress core still can’t: posts grouped under year, month, category or author headings; category and term indexes; user directories; and combined Terms + Posts and Users + Posts lists. You control the output with a template of plain HTML and simple template tags, so the markup stays clean, semantic and completely yours. Place any list anywhere with the W4 Post List block, the [postlist id="123"] shortcode, or the classic widget. What can you build? Year/month archives — posts grouped under date headings Category, tag or custom taxonomy indexes — with or without each term’s posts listed underneath Author and user directories — list users by role, with avatars, bios and each user’s posts Filtered post lists — any post type, filtered by status, taxonomy terms, custom fields, dates, authors, parents and more Media lists — image and attachment lists by mime type Five list types Posts Terms Users Terms + Posts Users + Posts Query options (Posts) Post type, status and mime type Search keyword Include/exclude posts by ID, exclude the current post Filter by parent, author, taxonomy terms (tax query), custom fields (meta query) and dates (date query) Items per page, with multi-page pagination Group results by Year, month, or month + year Category, tag or any custom taxonomy Author Parent Order results by ID, title, slug, publish date, modified date, menu order, comment count, custom field value, or random Pagination Next/previous links or numeric navigation, with optional AJAX page loading Full control over the output Output is template-driven: every list has an HTML template with template tags like [post_title], [post_permalink], [featured_image], [post_author_name] and [post_meta key="..."]. Start from a ready-made template — cards, archives, category indexes, user directories — and tweak it, or write your own markup for pixel-perfect control. A live preview in the editor shows your changes before you save. If you want a drag-and-drop visual builder, this plugin isn’t that — it keeps you close to your own HTML, which is exactly why themes and developers like it. See the full template tag reference and live examples with copy-paste templates. Lightweight, independently measured WP Hive independently measures W4 Post List at 19 KB memory usage and +0.05 s page-speed impact — better than 99% of the plugins they test. No bundled frameworks, no frontend bloat. Privacy Policy W4 Post List uses Appsero SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster & make product improvements. Appsero SDK does not gather any data by default. The SDK only starts gathering basic telemetry data when a user allows it via the admin notice. We collect the data to ensure a great user experience for all our users. Integrating Appsero SDK DOES NOT IMMEDIATELY start gathering data, without confirmation from users in any case. Learn more about how Appsero collects and uses this data.