Showtime Documentation
Showtime is a single Craft CMS 5 plugin — one handle, one license, one price — that mounts Owl (events and calendars), Stub (bookings and appointments), and Headcount (memberships and subscriptions) as internal modules.
Start here
Installation
Requirements, Composer, and first-run configuration on a clean site.
Upgrading from standalone
Already running Owl, Stub, or Headcount? Showtime adopts it in place.
Configuration
Shared Stripe and email settings, per-module overrides, and config files.
What’s included
Everything each bundled plugin brings, and where its own docs live.
Member perks
Discount or gate a booking service behind a membership plan.
Control panel
The unified nav and the bundle dashboard.
Permissions
One heading, unchanged keys, and what each permission unlocks.
Console commands
Deploy, maintenance, and scheduled tasks across all three modules.
How it works
The mount contract, licensing, and why nothing is cut down.
Troubleshooting
Ambiguous class resolution, missing settings, and other traps.
The 60-second version
On a site that has never run any of the three:
composer require justinholtweb/craft-showtime
php craft plugin/install showtime
On a site that already runs one of them standalone — note that you do not uninstall it first:
composer require justinholtweb/craft-showtime
php craft plugin/install showtime # adopts every already-installed bundled plugin
composer remove justinholtweb/craft-stub justinholtweb/craft-headcount justinholtweb/craft-owl
Then set your Stripe credentials once, at Settings → Plugins → Showtime, and they reach every module that needs them.
Requirements
- Craft CMS 5.6.0 or later
- PHP 8.2 or later
- MySQL 8.0+ or PostgreSQL
- Craft Commerce 5.0+ — optional, only for Owl’s event ticketing
- A Stripe account for paid bookings or memberships; PayPal optional for memberships
Where the bundled plugins’ own docs live
Showtime doesn’t reimplement the three plugins, so their existing documentation applies verbatim. Anything about creating services, building recurrence rules, or gating content is documented on that plugin’s own site:
- Owl documentation — events, calendars, recurrence, ICS, GraphQL, ticketing
- Stub documentation — services, providers, availability, the booking form, Stripe
- Headcount documentation — plans, gating, drip content, webhooks, the REST API
These pages cover the parts that are specific to running them as a bundle.