WordPress.org

If the plugin detects that there is a custom post type registered with a particular name (either 'event' or '*_event'), it steps in and does a number of useful additional things:

• For front-end queries fetching events, returned posts are sorted chronologically, the oldest first.
• For front-end queries fetching events, by default only future events are returned. This can be overridden by setting the custom parameter slt_all_events in your posts query to true. Alternatively, use slt_past_events (set to true) to get only past events.
• By default events are ordered chronologically. To reverse the order, set slt_reverse_events to true.
• In the admin listing page for events, an 'Event date' column is added.
• For particular queries, all actions performed by this plugin can be disabled by setting the custom parameter disable_simple_events in your posts query to true.

IMPORTANT: The automatic event filtering only kicks in with front-end queries done using WP_Query. Use this rather than get_posts.

In addition, this function is provided for convenience. If an event date exists for the post in question, it returns that; if not, it returns the standard post date.

<?php slt_se_get_date( $the_post = null ) ?>

• $the_post (object) (optional) (default: global $post object)

NOTE: An Event Date custom field will be added to the event edit screen automatically if my Custom Fields plugin is active. Otherwise, make sure your event post type supports custom-fields (see [register_post_type](http://codex.wordpress.org/Function_Reference/register_post_type), and add dates to events with the format YYYY/MM/DD, e.g. 2011/12/21 - this format is required to allow sorting by this field.

NOTE: The filtering performed by this plugin currently doesn't work well with get_posts - for now, create custom loops with WP_Query.

Development code hosted at GitHub.