This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.



AStickyPostOrderER lets you customize the order in which posts are displayed per category, per tag, or over-all, in WordPress 2.3+ blog.

Useful when using WordPress as a Content Management System.

Now with the ability to override itself.

How to:

Once the plugin is installed, go to „Tools“, „AStickyPostOrderER“.

The plugin displays a list of your categories as well as a list of tags in use.
The category and tag names are links (used to make ‘Sorties’) each followed by radio buttons and a Limit field.

Sorties: Click a category or tag’s name below to manually create an order of some or all of its contained posts to be shown before the default ordered posts in that category or tag, or re-arange all posts as they apear on home(index) and archive pages.

(Please Note: You have to individually set order for each category or sub category you want to order posts in, if enough people express it as a requirement I’ll add functionality for the plugin to propagate order set in the index view to either all- or specific categories tags. Mail me if you need this.)


Meta: Use the radio buttons to specify meta-stickyness, respectively:

  1. Super-sticky: Show before anything else (you can set a limit for how many posts from this cat or tag should be given this preferential treatment, e.g. if you want the latest post with the tag ‘events’ to show before anything else in any category listing that contains that post place 1 in the text field next to the ‘events’ tag and set it’s radio button set to ‘Super-sticky’ )

  2. Sub-sticky: Show after individually ordered posts (‘Sorties’) for given view but before un-sorted posts

  3. Default: Treat normally (except for individually ordered posts)

  4. Droppy: Show only after everything else
    and remember to click ‘update meta-stickyness’ at the bottom of the page for your changes to, ahemmm, ‘stick’ . . .


If you want to have posts listed without the customised order you can do that by having ‘?aspo=vanilla’ in the url, or if you created a listing with query_posts add aspo=vanilla, eg. ‘query_posts(‘cat=13&showposts=10&aspo=vanilla’);’



Standard WordPress plugin installation procedure


There are no reviews for this plugin.

Contributors & Developers

“AStickyPostOrderER” is open source software. The following people have contributed to this plugin.


Translate “AStickyPostOrderER” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.


0.3.1 (2010/03/15)
* Created ability to override sorting via url query string parameter or query_posts
* Some themes use secondary loops that caused posts to not show up in some situations, partially addressed. There is still a challenge with using e.g. some widget plugins like CategoryPosts if looking at a category page that is sorted the widget’s listing will also be sorted by astickypostorderer’s order – while one might expect that to remain in reverse cronological order. If this is a problem consider replacing WP_Query with query_posts which might solve it for you

0.2.3 (2009/08/20)
* Added pagination for listing of posts in the admin screens (2008/06/09)
* Fixed so when posts are deleted aStickyPostOrderER forgets about them (in stead of retaining them in the order DB tables)
(Will code up a clean up to take care of existing ‘holes’ from previous versions in the not too distant future.)
* Incorporated a search filter with pagination for tags (2008/04/28)
* Fixed parent categories not showing order in WordPress 2.5
* Fixed weirdness previously resulting from removing posts from being ordered
* Added index.php (html version of readme with link to host site)


  • Clean up blank and missing elements that still show empty rows in admin
  • Drag and drop
  • Add search, alphabetical sorting and quick-links to admin post sorting screens
  • Find better approach to the WP_Query issue