Front-end submission

Owl lets visitors submit events from the front end — community calendars, listings, “add your event” forms — with validation and spam protection, and without a control-panel account. Included in the free Lite edition.

A basic submission form

Post to Owl’s save action from a normal Craft form. New submissions are created disabled by default, so you can review and approve them before they appear:

{{ csrfInput() }} {{ actionInput('owl/events/save') }} {{ hiddenInput('calendarId', concerts.id) }} {# honeypot — leave empty #}

Validation & errors

If a submission fails validation, Owl flashes errors and returns the submitted values so you can re-render the form, exactly like entries. Required fields, date sanity (end after start) and your calendar’s custom-field rules are all enforced.

Spam protection

Front-end submission supports an optional honeypot field and per-IP rate limiting, so public forms don’t become a spam vector. Configure both in settings.

Moderation

Because submitted events are ordinary disabled elements, they show up in Owl → Events for review. Enable one to publish it (and materialise its occurrences); leave it disabled or delete it to reject.

More in Site Features

Pairs well with Owl

The bigger pieces a client asks for by name. Events, bookings, memberships, courses, reviews, a support desk, job listings and the rest.