Editors can choose daily, weekly or monthly patterns with an optional end date or occurrence count.

What happens when attendance is limited?

The package manages registration capacity and waitlists for event occurrences.

How do visitors follow the programme?

Visitors can browse public listings and calendars and subscribe to an ICS feed.

Released

Events

Publish a recurring programme and manage each date's attendance.

Version: 1.1.10
Released: 10 November 2026
Requires: Discovery Foundation, Navigation, Publishing Studio
Licence: Commercial

Price £39.00

Check access and installation

Events admin table with recurring event status and registration counts — Events index

Price and access
Review the price, licence and availability before deciding what to adopt.
What it solves
See the problem this extension removes, what your site gets, and the answers to common questions.
Your workflow
Read how the package is used and what your application needs to provide.
Product captures
Review the available captures and see which part of the workflow each screen demonstrates.
Capabilities
See which jobs this extension supports and which parts it adds to your site.
Project fit
Decide what this removes from your workload and what your application still needs to supply.
Installation
Check the setup steps before adding the package to a project.
Release evidence
Review the available release, maintenance and package-review information.

Outcome

What it solves

The problem

Our organisers keep recreating dates and tracking attendance for recurring events.

What your site gets

The site has a recurring event programme with managed registrations.

Questions buyers ask

Can an event repeat?: Editors can choose daily, weekly or monthly patterns with an optional end date or occurrence count.
What happens when attendance is limited?: The package manages registration capacity and waitlists for event occurrences.
How do visitors follow the programme?: Visitors can browse public listings and calendars and subscribe to an ICS feed.

Usage

Use it in your project

Set up the event once, review its occurrences and give visitors a clear registration path. Staff can manage capacity and waitlists as plans change.

Picture it on your site

For a recurring workshop, begin with one event and its actual occurrences, capacity and registration route. Review what a visitor sees before staff start using the wider programme. Keeping the event information together helps avoid conflicting dates, while the team still owns the programme, attendance process and any external booking arrangements.

6 captures

Create event form with schedule, recurrence, venue, and capacity settings — Create event form

Edit event form showing generated occurrence and registration state — Edit event form

Event venues admin table with reusable address and map details — Event venues management

Event occurrences admin table with generated schedule and capacity state — Event occurrences management

Event registrations admin table with confirmed, pending, and waitlisted attendees — Event registrations management

Included

Manage conversations and responses

Manage recurring events, venues and dated occurrences.
Publish calendars and feeds with registration and waitlist support.

Is this right for your project?

Give responses an owner

Collecting a message is only useful when somebody knows what to do next. Decide who reviews incoming activity, what a visitor should hear back and when a record can be closed or removed. The package can provide the supported collection or moderation workflow; your team supplies response times, escalation rules and the tone of the conversation.

Follow a visitor through the workflow

Try the public interaction as a visitor, then find the resulting record in the admin and complete the staff task. Check validation, permissions and what happens when a response cannot be delivered. This is a better launch check than testing the form alone, because it proves that the interaction reaches the people responsible for handling it.

Licence £39.00 / 12 months

One customer organisation; up to 5 named users. Each entitlement covers one production website or application and up to two non-production environments, with a maximum of three active installations.

12 months of protected downloads, updates and included standard support.

+ VAT where applicable

You may ask Capell for a full refund within 14 days of purchase. Requests are assessed case by case against the recorded order, access and support history. This applies to live paid first-party packages; third-party author sales have separate terms. Read the Refund Policy

Renewal is charged at the price current when you renew. The price is shown before you pay.

Review site impact

Marketplace listings can describe install impact and data access.

This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.

Paid checkout adds access to the purchasing account after payment. Review compatibility and site impact, then follow the installation steps for this package.

Open the Capell demo

This listing has no page of its own in the demo. Open the demo to see Capell running.

Details

At a glance

Version: 1.1.10
Released: 10 November 2026
Compatibility: Capell 1.x from 1.0.76; PHP 8.x from 8.4
Support: Included standard support
Data access: Reads and writes Capell content structures required by the package; public output receives rendered content only.
Licence: Commercial

Installation impact

Before you install

Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.

Admin and public surfaces: The package declares: administration screens, frontend integration, command-line operations, public routes. Review the release documentation for configuration and exposure in your application.
Data and migrations: Database migrations are declared. The installation flow can change your database; back up data and review the release migrations before installing. Reads and writes Capell content structures required by the package; public output receives rendered content only.
Background work: Scheduled background work is declared. Keep the host scheduler running and check the release documentation for queue workers, frequencies and pruning configuration.
Access controls: Package access controls are declared. Review role grants and the host authorisation configuration before allowing users into the new workflow.
Removal and retained data: A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.

01

Prepare protected Composer access

Sign in to the account with active package access. Open its generated installation instructions and configure the protected Composer repository before running the commands below. Keep access credentials private. Open my package installation instructions
02

Require the package

composer require capell-app/events
03

Install the extension

php artisan capell:extension-install capell-app/events
04

Activate the package licence

In this site’s Admin, open Marketplace, find Events (capell-app/events), and activate its licence using the purchase licence key if requested. This activates the package you have already installed. Wait for the Marketplace operation to succeed before continuing; keep its queue worker running.
05

Report the installed package

php artisan capell:marketplace:heartbeat

Release and review evidence

Maintenance

Release activity stays visible

These dates come from approved package releases, so you can see the release trail before installing.

Latest approved release: v1.1.10 Nov 10, 2026
Recent activity: 15 approved releases in the last 12 months

Capell reviewed

Review evidence for this release

Events and registration package reviewed: public RSVP submissions are throttled and built server-side from validated fields, with one internal tidy-up noted on the data models.

Review reduces risk, but it is not a permanent security guarantee.

Automated checks passed

AI-assisted analysis completed

Human sign-off completed

Reviewed version: 1.1.10
Approval date: Nov 8, 2026

Areas reviewed

Strict, maintainable PHP
Presentation-only public views
Actions and typed boundaries
Clean anonymous public output
Authorisation and input safety
Declared package boundaries
Manifest and migration integrity
Compatibility and interoperability
Meaningful behavioural tests
Security and supply-chain checks
Performance and operational behaviour
Theme delivery quality where applicable
Marketplace claims matched to behaviour
AI-assisted analysis with human accountability

Accepted limitations

Calendar feeds are served at unauthenticated URLs so external calendar applications can subscribe to them.

Read the full Capell review method

Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.

Changelog

Release notes and maintenance evidence

Version history

Showing the 10 most recent of 15 approved releases

v1.1.10
Nov 10, 2026

Release notes

Full Changelog: https://github.com/capell-app/events/compare/v1.1.9...v1.1.10
v1.1.9
Nov 2, 2026
v1.1.8
Oct 28, 2026
v1.1.7
Oct 20, 2026
v1.1.6
Oct 17, 2026
v1.1.5
Oct 10, 2026
v1.1.3
Oct 9, 2026
v1.1.2
Oct 8, 2026
v1.1.1
Oct 8, 2026
v1.1.0
Oct 7, 2026

Before checkout

Know who owns access and what happens next

Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.

Who processes the payment and taxes?

Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.

Which account owns the licence?

The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.

How does the site receive package access?

The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.

What happens if checkout is cancelled or expires?

No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.

How do I request a refund?

There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy

What should I do if access does not appear?

Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.

Events