Events

Developed by

Download

Plugin Description

Events allows events such as webinars or conferences to be created via a custom post type.

Description

Events allows events such as webinars or conferences to be created via a custom post type; categories, excerpt, details, start and end dates and times and a featured image are all supported.

In the options set defaults for the widget and shortcode.

Multiple widgets can be created, each assigned to display a category; settings for title, image size and limit for number of events to list can be set per widget.

The event shortcode accepts three parameters:

  • slug to select specific event.
  • width to set the size of the featured image.
  • height to set the size of the featured image.

Shortcode usage is [event slug="december-2026" width=150 height=150]; all parameters are optional and will use the defaults set via the settings page if not supplied.

The events shortcode accepts four parameters:

  • category to restrict the output to the selected category.
  • width to set the size of the featured image.
  • height to set the size of the featured image.
  • limit to restrict the number of events to display.

Shortcode usage is [events category="webinars" width=150 height=150 limit=5]; all parameters are optional and will use the defaults set via the settings page.

All “is this event over yet” checks use your site’s configured timezone (Settings > General > Timezone in the admin), not the timezone of the server itself.

Installation

  • Download the latest release of the plugin from GitHub.
  • Upload the entire zip file using the Plugins upload function in your ClassicPress admin panel.
  • Activate the plugin.
  • Configure relevant settings via the settings page in the admin control panel (azurecurve menu).

== Screenshots ==

  1. Create new event in the custom post type.
  2. Add widget to widget area, select category and amend defaults if necessary.
  3. Widget displaying events in sidebar.
  4. Page showing output of events shortcode.

Frequently Asked Questions

Can I translate this plugin?

Yes, the .pot file is in the plugin’s assets/languages folder and can also be downloaded from the plugin page on https://development.azurecurve.co.uk; if you do translate this plugin, please sent the .po and .mo files to [email protected] for inclusion in the next version (full credit will be given).

Is this plugin compatible with both WordPress and ClassicPress?

This plugin is developed for ClassicPress, but will likely work on WordPress.

What happened to the To X integration?

The To X integration (and the earlier To Twitter integration it replaced) has been removed as of version 2.1.0, following changes to X’s API that made the integration unviable. Events no longer posts or reposts to X in any way; existing per-event autopost settings are no longer used and can be ignored.

Will uninstalling this plugin delete my events?

Not unless you’ve explicitly opted in via the “Delete event data on uninstall” checkbox on the Widget tab, which is off by default.

Changelog

Version 2.0.1

  • Update settings page and instructions to clarify purpose of fields.

Version 2.0.0

  • Rebuilt on azurecurve’s current, modular plugin pattern (namespaced, split across includes/ files, shared cross-plugin admin menu and tabs component).
  • Replaced all jQuery with vanilla JavaScript.
  • Fixed a timezone bug: scheduled posts/reposts to X, and “is this event over yet” checks, previously used the server’s default PHP timezone rather than the site’s configured timezone, which could post on the wrong day or at the wrong time. A single timezone-aware helper is now used everywhere a date is displayed, compared, or scheduled.
  • Renamed the “To Twitter” integration to “To X”, following azurecurve’s own retirement of To Twitter in favour of a new To X plugin. Existing “to-twitter” settings and per-event autopost settings are migrated automatically.
  • Added an opt-in “Delete event data on uninstall” setting; uninstalling now always clears any pending scheduled posts/reposts, and – only if that setting is enabled – also deletes event posts and their metadata (previously, uninstalling never deleted this data, silently, with no way to opt in).
  • Added a “flush_rewrite_rules()” call on activation, fixing event/category URLs occasionally 404ing until something else happened to flush rewrite rules.
  • Fixed a bug where the End Date field was marked as required despite the help text saying to leave it blank for a one-day event; End Date is now genuinely optional and defaults to the Start Date when left blank.
  • Added Category, Start Date/Time and End Date/Time columns (Start Date/Time sortable) to the Events admin list page.
  • Changed the default date format from m/d/Y to d/m/Y.
  • Changed the displayed date/time range format from “start date-end date start time-end time” (e.g. “10/09/2026-13/09/2026 10:00-16:00”) to “start date start time -end date end time” (e.g. “10/09/2026 10:00 -13/09/2026 16:00”) for multi-day events.
  • Added a Location field (free text) to events, set alongside the start/end dates. Location is shown in the Events admin list column, the Events widget, and the [events]/[event] shortcode output, directly below the date range.
  • Renamed the “Event Dates” metabox to “Event Details” to reflect that it now also holds Location.
  • Fixed several bugs found during the rebuild: missing output escaping in the Event Dates metabox; a broken settings-saved notice caused by a reference to an undefined variable; a “Use Featured Image” checkbox label that never rendered due to a missing echo; two strings using the wrong translation text domain; a missing defensive check that could emit a PHP warning for an event with incomplete date metadata; use of extract() in the widget class; unversioned/stale-versioned enqueued assets; a generic (rather than plugin-specific) Update Manager image-path filter that could affect other azurecurve plugins’ icons; unescaped taxonomy output; and a metabox nonce action tied to a file path that would have broken under the new file structure.
  • Removed the To Twitter integration, following changes to Twitter’s API that made it nonviable.
  • Update readme.md and remove readme.txt (not required for ClassicPress).
  • Update azurecurve menu.

Version 1.3.5

  • Fix bug with short PHP declaration.
  • Add missing Requires PHP tag in plugin header.

Version 1.3.4

  • Update plugin header and readme for compatibility with ClassicPress Directory v2.
  • Update Update Manager to version 2.5.0.

Version 1.3.3

  • Update readme file for compatibility with ClassicPress Directory.

Version 1.3.2

  • Update readme files.
  • Update language template.
  • Fix bug with azurecurve menu.

Version 1.3.1

  • Update azurecurve menu.
  • Update readme files.

Version 1.3.0

  • Update translations to escape strings.
  • Update azurecurve menu and logo.

Version 1.2.2

  • Remove extraneous code.

Version 1.2.1

  • Fix bug with saving of tweet and retweet days before options.

Version 1.2.0

Version 1.1.1

  • Remove debug code.

Version 1.1.0

  • Add no event found message.
  • Add option to display widget only when events found.
  • Add function to handle multilevel default options correctly.
  • Fix bug with default category not working when adding widget.

Version 1.0.1

  • Update screenshots.

Version 1.0.0

  • Initial release.

Other Notes

About azurecurve

azurecurve was one of the first plugin developers to start developing for ClassicPress; all plugins are available from azurecurve Development and are integrated with the Update Manager plugin for fully integrated, no hassle, updates.

The plugins available from azurecurve are: