Andrew Norcross

Steve Grunwell

Liquid Web

<p>Sticky Tax enables posts to be made “sticky” within a specific category or tag. Ideal for cornerstone content or important stories, Sticky Tax lets blogs maintain chronological post archives, while keeping the most important content at the top of the list.</p>
<h3>Why might I want this?</h3>
<p>Let’s imagine Chris, a long-time blogger with lots of traffic coming to his site. He’s worked hard to categorize all of his content, but there are a few posts that he wants to make sure are the first thing people see when they hit a category landing page.</p>
<p>Using WordPress’ default behavior, these important pieces of content will eventually get lost behind pagination, just because they’re not the newest posts in the category.</p>
<p>With Sticky Tax, Chris can highlight the most important posts in a category, whether they were written last week or last year!</p>
<h3>Usage</h3>
<p>After installing and activating Sticky Tax, a new “Promote Post” meta box will appear on the post edit screen, with a list of terms for any public taxonomies registered on your site.</p>
</p>
<h3>On the front-end</h3>
<p>archive. Each sticky post even gets a <code>.sticky-tax</code> class added to it, enabling you to apply custom styling for your sticky content!</p></p>


Sticky Tax

Make posts sticky within the context of a single category, tag, or custom taxonomy term.

Luis Rodrigues

<p>Sticky posts for WordPress, improved.</p>
<p>This plugin addresses the following issues and limitations found in the core’s implementation of sticky posts:</p>
<ul>
<li>Only the core <code>post</code> type supports this feature.</li>
<li>Sticky posts are added in front of your homepage’s results, yielding more posts than the configured per-page setting.</li>
<li>Sticky posts reappear as you navigate further into the archive.</li>
<li>Sticky posts are prepended to your results when querying specific posts with <code>post__in</code>.</li>
<li>Difficult to include sticky posts in custom queries.</li>
</ul>
<p>Some of these issues cause strange behaviour (like when using the REST API) and complicate the creation of custom homepage layouts.</p>
<p>At one point we decided to stop fighting the core and partially reimplemented the feature using custom post fields and meta queries, giving you:</p>
<ul>
<li>Sticky posts for all non-hierarchical post types.</li>
<li>Post stickiness on post type and taxonomy archives.</li>
<li>Respect for your configured per-page setting, with stickies spilling over onto the next page.</li>
<li>Duplicates filtered from your archive pages.</li>
<li>The ability to sort by stickiness on virtually any <code>WP_Query</code> lookup.</li>
<li>Support for the <a href="https://developer.wordpress.org/reference/functions/is_sticky/" rel="nofollow ugc"><code>is_sticky()</code></a> function.</li>
<li>A predictable WordPress REST API experience.</li>
<li>A slight SQL query overhead (sorry!)</li>
</ul>
<p>Post Glue will continue to save post IDs to the <code>sticky_posts</code> option, meaning you’ll retain some core functionality even if you decide to stop using the plugin.</p>
<p>Please follow and contribute to Post Glue’s development on <a href="https://github.com/log-oscon/post-glue" rel="nofollow ugc">Github</a>.</p>


Sticky Tax vs Post Glue