Settings

Owl’s settings live under Owl → Settings, and can be overridden in code with a config/owl.php file for environment-specific values and version control.

Occurrence horizon

• Generation horizon — how far into the future Owl materialises occurrences (default ~2 years). Larger horizons mean more rows but further-out feeds and views.
• Horizon top-up — a scheduled task rolls the horizon forward over time, so far-future dates keep appearing as time passes.

Defaults

• Default timezone — the timezone new events start with (defaults to the system timezone).
• Demo templates — whether to register the bundled FullCalendar demo templates.

Front-end submission

• Enable honeypot — adds an invisible field that bots tend to fill in.
• Rate limiting — caps submissions per IP over a window.
• Default status — whether submitted events start enabled or disabled (disabled is recommended for moderation).

Config file overrides

Create config/owl.php to set values per environment. Settings in this file take precedence over the control panel and are read-only there:

 '+2 years',
    'defaultTimezone' => 'America/New_York',
    'enableHoneypot' => true,
];

Queue & cron

Owl relies on Craft’s queue to generate occurrences and on a scheduled task to roll the horizon forward. In production, run the queue with php craft queue/run (or a daemon) and schedule Craft’s console so horizon top-ups happen on time. See Recurrence.