Exception Reports
Get useful failure reports to the people who maintain the site.
- Version
- 1.1.0-beta.49
- Released
- 20 October 2026
- Licence
- Free
Price Free
Check access and installationCheck compatibility before using this Beta extension
Beta does not mean production-ready. Review compatibility, support, site impact, and likely upgrade work before enabling it.
Check your application before checkout
Use it in your project
Configure email recipients or a signed webhook endpoint for exception reports. Grouped digests and rate limits help keep repeated failures manageable.
Picture it on your site
For an operational handover, choose a recipient or signed webhook that someone will actually monitor, then agree which failures need immediate attention. Review how repeated exceptions appear in the digest. A useful alert points the operator towards investigation; it does not make an application healthy merely because a notification was delivered.
No workflow evidence published yet
No workflow screenshots are published. Use the demo or documentation to understand the extension before installing.
Maintain and monitor your site
- Deliver sanitised exception context by email or webhook.
- Group repeated reports and limit notification volume.
Is this right for your project?
Make a signal actionable
An operational screen is most useful when a warning has an owner and a next step. Decide which checks matter to your site, who reviews them and how they distinguish an expected state from a failure. The package supplies its supported observations or controls; the application and hosting environment still determine the queues, schedules, credentials and infrastructure those checks depend on.
Exercise the recovery path
On a safe local or staging environment, follow one representative task from detection to resolution and confirm the public result afterwards. Check what happens when a dependency is unavailable and how the team knows the issue has cleared. Visible status is useful evidence, but it should sit alongside your deployment, monitoring and recovery procedures rather than replace them.
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/exception-reports -
02
Install the extension
php artisan capell:extension-install capell-app/exception-reports
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.0-beta.49 Oct 20, 2026
- Recent activity
- 10 approved releases in the last 12 months
Review evidence for this release
Error reporting package reviewed with no defects found; outbound reports are redacted, signed, pinned to the resolved destination address and never follow redirects.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.0-beta.49
- Approval date
- Oct 16, 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
- Stack traces are omitted from emails and webhooks unless an operator opts in, which makes the default reports less detailed by design.
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.0-beta.49Oct 20, 2026 -
v1.1.0-beta.48Oct 17, 2026 -
v1.1.0-beta.45Oct 9, 2026 -
v1.1.0-beta.44Oct 8, 2026 -
v1.1.0-beta.43Oct 8, 2026 -
v1.1.0-beta.42Oct 7, 2026 -
v1.1.0-beta.41Oct 4, 2026 -
v1.1.0-beta.40Oct 1, 2026 -
v1.1.0-beta.39Sep 29, 2026 -
v1.1.0-beta.38Sep 23, 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.