Events
Publish a recurring programme and manage each date's attendance.
- Version
- 1.1.7
- Released
- 20 October 2026
- Requires
- Discovery Foundation, Navigation, Publishing Studio
- Licence
- Commercial
Price £39.00
Check access and installationOn this page
-
Price and access
Review the price, licence and availability before deciding what to adopt.
-
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.
Check your application before checkout
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.
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.
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
Your renewal price stays locked while you renew continuously, including during the grace period. After a full lapse, renewal uses the current list price.
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. Add a free package to your account, then review compatibility and site impact before installing it.
Explore the available extensions on the demo site.
Before you install
Run the commands below in your Capell application. Required dependencies are listed above. After installing a theme, select it for your site in Admin.
-
01
Require the package
composer require capell-app/events -
02
Install the extension
php artisan capell:extension-install capell-app/events
Release and review evidence
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.7 Oct 20, 2026
- Recent activity
- 12 approved releases in the last 12 months
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.
- Reviewed version
- 1.1.7
- Approval date
- Oct 19, 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.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
10 releases-
v1.1.7Oct 20, 2026 -
v1.1.6Oct 17, 2026 -
v1.1.5Oct 10, 2026 -
v1.1.3Oct 9, 2026 -
v1.1.2Oct 8, 2026 -
v1.1.1Oct 8, 2026 -
v1.1.0Oct 7, 2026 -
v1.1.0-beta.46Oct 4, 2026 -
v1.1.0-beta.45Oct 1, 2026 -
v1.1.0-beta.44Oct 1, 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?
Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.
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.