agenticdaisy

<p>WebCalendar gives your WordPress site a clean, responsive calendar with the features you actually need — recurring events, iCal import, remote sync, email reminders, and fine-grained permissions — without the complexity.</p>
<p><strong>Calendar Views & Display</strong></p>
<ul>
<li>Month, week, and day views with smooth AJAX navigation — no page reloads</li>
<li>Responsive design that adapts to any theme and screen size</li>
<li>Color-coded categories for visual organization</li>
<li>Gutenberg blocks (Calendar + Upcoming Events) and <code>[webcalendar]</code> shortcode</li>
</ul>
<p><strong>Event Management</strong></p>
<ul>
<li>Recurring events — daily, weekly, monthly, and yearly patterns with RRULE support</li>
<li>Edit a single instance or the entire series</li>
<li>File attachments via the WordPress Media Library</li>
<li>Conflict detection warns you about overlapping events</li>
<li>Public, Private, and Confidential visibility levels</li>
</ul>
<p><strong>Import, Export & Sync</strong></p>
<ul>
<li>Import <code>.ics</code> files from Google Calendar, Outlook, Apple Calendar, or any iCal source</li>
<li>Export your calendar in iCalendar format</li>
<li>Subscribe to remote iCal feeds with automatic hourly sync</li>
<li>Import public holidays for any country</li>
</ul>
<p><strong>Collaboration & Permissions</strong></p>
<ul>
<li>Invite WordPress users to events with email notifications</li>
<li>Event reminders via WP-Cron</li>
<li>36 granular capabilities mapped to WordPress roles — control who can view, create, edit, and manage events</li>
</ul>
<p><strong>SEO & Sharing</strong></p>
<ul>
<li>Single event pages with SEO-friendly permalinks</li>
<li>Schema.org Event JSON-LD, Open Graph, and Twitter Card meta tags</li>
<li>Social share buttons and “Add to Google/Outlook/Yahoo” one-click buttons</li>
</ul>
<p><strong>For Developers</strong></p>
<ul>
<li>Full REST API for events, categories, holidays, and remote calendars</li>
<li>Built on Clean Architecture with <code>webcalendar-core</code> business logic library</li>
<li>PSR-4 autoloading, PHPStan Level 9, 1100+ automated tests</li>
<li>All calendar data in dedicated <code>webcal_*</code> tables — no Custom Post Types</li>
</ul>
<p><strong>Want Even More?</strong></p>
<p><a href="https://agenticdaisy.com/webcalendar/" rel="nofollow ugc">WebCalendar Pro</a> is a separate premium plugin that adds:</p>
<ul>
<li><strong>Appointment Booking</strong> — public scheduling with availability management</li>
<li><strong>Google & Outlook Sync</strong> — two-way OAuth synchronization</li>
<li><strong>Multisite Network Support</strong> — shared calendars across a WordPress network</li>
<li><strong>White-Labeling</strong> — remove all WebCalendar branding</li>
<li><strong>Priority Support</strong> — 24-hour response time SLA</li>
</ul>
<p>The free version you’re using right now is fully functional with zero locked features. Pro adds capabilities that aren’t included here.</p>
<p><strong>Technical Note: Database Architecture</strong></p>
<p>This plugin integrates <code>webcalendar-core</code>, a framework-agnostic Composer library that provides all calendar business logic (events, recurrence, iCal, permissions) through 17 repository classes. These repositories require PDO and use exclusively parameterized prepared statements — no raw SQL concatenation. WordPress-specific data (users, options, capabilities) is accessed via <code>$wpdb</code> through the plugin’s Bridge layer (<code>WpUserRepository</code>, <code>WpConfigRepository</code>, etc.). See <code>src/Bridge/PdoFactory.php</code> for the connection factory.</p>
<h3>External Services</h3>
<p>This plugin connects to the following third-party services:</p>
<h4>Nager.Date API</h4>
<p>Used for importing public holidays via WebCalendar > Holidays.<br />
* Endpoint: https://date.nager.at/api/v3/<br />
* <a href="https://date.nager.at/LegalNotice" rel="nofollow ugc">Terms of Use</a><br />
* <a href="https://date.nager.at/Privacy" rel="nofollow ugc">Privacy Policy</a></p>
<h4>Google Calendar Public Feeds</h4>
<p>Alternative holiday source. Fetches public .ics files from Google.<br />
* Endpoint: https://calendar.google.com/calendar/ical/<br />
* <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a><br />
* <a href="https://policies.google.com/terms" rel="nofollow ugc">Google Terms of Service</a></p>
<h4>Thunderbird Holiday Calendars</h4>
<p>Alternative holiday source via community-maintained .ics files.<br />
* Endpoint: https://www.thunderbird.net/media/caldata/<br />
* <a href="https://www.mozilla.org/about/legal/terms/mozilla/" rel="nofollow ugc">Mozilla Terms of Use</a><br />
* <a href="https://www.mozilla.org/privacy/" rel="nofollow ugc">Mozilla Privacy Policy</a></p>
<h4>Remote Calendar Sync (User-Configured)</h4>
<p>When remote iCal subscriptions are configured, the plugin fetches .ics data from<br />
those URLs via HTTP GET. No user data is transmitted to these services.</p>
<h4>OpenStreetMap / Nominatim</h4>
<p>When a single event page has a location and the map provider is set to OpenStreetMap<br />
(the default), the plugin geocodes the address via the Nominatim API and displays a<br />
map using OpenStreetMap tile servers. The event location string is sent as a search<br />
query. No user personal data is transmitted.<br />
* Geocoding endpoint: https://nominatim.openstreetmap.org/search<br />
* Tile server: https://tile.openstreetmap.org/<br />
* <a href="https://wiki.osmfoundation.org/wiki/Terms_of_Use" rel="nofollow ugc">OpenStreetMap Terms of Use</a><br />
* <a href="https://operations.osmfoundation.org/policies/nominatim/" rel="nofollow ugc">Nominatim Usage Policy</a><br />
* <a href="https://wiki.osmfoundation.org/wiki/Privacy_Policy" rel="nofollow ugc">OpenStreetMap Privacy Policy</a></p>
<h4>Google Maps Embed API</h4>
<p>When the map provider is set to Google Maps in settings, single event pages display<br />
an embedded Google Map for the event location. The event location string and your<br />
Google Maps API key are sent to Google. No other user data is transmitted.<br />
* Endpoint: https://www.google.com/maps/embed/v1/place<br />
* <a href="https://cloud.google.com/maps-platform/terms" rel="nofollow ugc">Google Maps Platform Terms of Service</a><br />
* <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></p>
<h4>Add to Calendar Links</h4>
<p>Single event pages include “Add to Calendar” buttons that generate links to Google<br />
Calendar, Outlook.com, and Yahoo Calendar. When a visitor clicks a button, the event<br />
title, date, time, location, and description are passed as URL parameters to the<br />
chosen service. No data is sent until the visitor clicks.<br />
* Google Calendar: https://www.google.com/calendar/render — <a href="https://policies.google.com/terms" rel="nofollow ugc">Terms</a> | <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy</a><br />
* Outlook.com: https://outlook.live.com/calendar/0/action/compose — <a href="https://www.microsoft.com/servicesagreement" rel="nofollow ugc">Terms</a> | <a href="https://privacy.microsoft.com/privacystatement" rel="nofollow ugc">Privacy</a><br />
* Yahoo Calendar: https://calendar.yahoo.com/ — <a href="https://legal.yahoo.com/us/en/yahoo/terms/otos/index.html" rel="nofollow ugc">Terms</a> | <a href="https://legal.yahoo.com/us/en/yahoo/privacy/index.html" rel="nofollow ugc">Privacy</a></p>
<h4>Social Sharing Links</h4>
<p>Single event pages include social sharing buttons for Facebook, X (Twitter), and<br />
LinkedIn. When a visitor clicks a button, the event page URL and title are passed as<br />
URL parameters to the chosen service. No data is sent until the visitor clicks.<br />
* Facebook: https://www.facebook.com/sharer/sharer.php — <a href="https://www.facebook.com/terms.php" rel="nofollow ugc">Terms</a> | <a href="https://www.facebook.com/privacy/policy/" rel="nofollow ugc">Privacy</a><br />
* X (Twitter): https://x.com/intent/tweet — <a href="https://x.com/tos" rel="nofollow ugc">Terms</a> | <a href="https://x.com/privacy" rel="nofollow ugc">Privacy</a><br />
* LinkedIn: https://www.linkedin.com/sharing/share-offsite/ — <a href="https://www.linkedin.com/legal/user-agreement" rel="nofollow ugc">Terms</a> | <a href="https://www.linkedin.com/legal/privacy-policy" rel="nofollow ugc">Privacy</a></p>
<h3>Development & Source Code</h3>
<p>Full unminified source for this plugin is included in this distribution under GPL-2.0-or-later — you do not need to download anything external to rebuild the compiled assets.</p>
<p><strong>What ships in this zip:</strong></p>
<ul>
<li><code>src/</code> — unminified React/JSX source for all admin components, frontend calendar, and the mini-calendar widget</li>
<li><code>build/</code> — the pre-compiled minified bundles (what the plugin actually loads at runtime)</li>
<li><code>package.json</code> + <code>package-lock.json</code> — Node build manifest and lockfile for reproducible <code>npm install</code></li>
<li><code>composer.json</code> — PHP dependency manifest</li>
</ul>
<p><strong>Rebuilding the compiled assets from source:</strong></p>
<p>Prerequisites: PHP 8.2 or higher with Composer 2, Node.js 20 or higher with npm 10.</p>
<ol>
<li><code>composer install</code> — install PHP dependencies</li>
<li><code>npm install</code> — install JavaScript build dependencies (@wordpress/scripts, React, Toast UI Calendar, Leaflet, Tiptap)</li>
<li><code>npm run build</code> — compile <code>src/index.js</code> and <code>src/frontend.js</code> into the minified bundles under <code>build/</code></li>
</ol>
<p>The compiled output in <code>build/</code> is byte-reproducible from the matching <code>src/</code> at the same version using this toolchain.</p>


WebCalendar

A modern calendar plugin with recurring events, iCal import/export, remote calendar sync, Gutenberg blocks, and access control.

digitaldonkey

Lukas Pawlik

Borislav Angelov

farmer paul

Justas Butkus

hubrik

Nicola Peluchetti

Yani

<p>An event calendar with native iCal / ICS import and export</p>
<h3>Features</h3>
<p>All features are provided in their entirety. <strong>No features are locked behind any add-ons</strong>.</p>
<ul>
<li><strong>Full iCal / ICS import & export</strong>
<ul>
<li>Automatically import external calendars</li>
<li>Categorize and tag imported feeds</li>
</ul>
</li>
<li><strong>Recurring events</strong>, including complex recurrence rules <a href="https://icalendar.org/iCalendar-RFC-5545/3-8-5-3-recurrence-rule.html" rel="nofollow ugc">(RFC 5545)</a></li>
<li>Filtering by category and tag</li>
<li><strong>Calendar sharing</strong> with Google Calendar, Apple iCal, Outlook, and any other system that accepts iCalendar (.ics) feeds</li>
<li>Month, week, day, and agenda views</li>
<li><strong>Upcoming Events</strong> Gutenberg block</li>
<li>Direct links to <strong>filtered calendar views</strong></li>
<li>Color-coded events by category</li>
<li>Featured event images and category images</li>
<li>SEO-optimized event pages</li>
<li>Mobile-friendly and responsive layouts</li>
<li>Embedded <strong>OpenStreetMap</strong></li>
<li>Theme options to customize your calendar appearence</li>
<li>Your calendar can be embedded into a WordPress page without needing to create template files or modify the theme.</li>
</ul>
<p><strong>Import events from other calendars</strong> and offer users the <strong>ability to subscribe to your calendar</strong>.</p>
<p>Importing and exporting iCalendar (.ics) feeds is one of the strongest features of the Event Calendar system. This allows you to manage your websites calendar by providing a public calendar from your Google, Apple or other calendar management software.</p>
<h3>Blocks</h3>
<p>You can embed the calendar by adding a <strong>OSEC Calendar Block</strong> to any page or post. Alternatively there is a shortcode available.</p>
<blockquote>
<p>[!WARNING]<br />
  At this time, only <strong>one calendar per page or post</strong> is supported.</p>
</blockquote>
<p>On the long run it’s planned to have a Rest API to allow the calendar being rendered with more modern frontend tools than the current, outdated, but nice old Bootstrap 3 stuff.</p>
<h3>Shortcodes</h3>
<h4>Calendar Views</h4>
<pre><code>[osec]                       // Default view per settings
[osec view="monthly"]
[osec view="weekly"]
[osec view="agenda"]
[osec view="daily"]
</code></pre>
<h4>Filtering</h4>
<p><strong>By category</strong></p>
<pre><code>[osec cat_name="Holidays"]
[osec cat_name="Lunar Cycles,zodia-date-ranges"]
[osec cat_id="1"]
[osec cat_id="1,2"]
</code></pre>
<p><strong>By tag</strong></p>
<pre><code>[osec tag_name="tips-and-tricks"]
[osec tag_name="creative writing,performing arts"]
[osec tag_id="1"]
[osec tag_id="1,2"]
</code></pre>
<p><strong>By post ID</strong></p>
<pre><code>[osec post_id="1"]
[osec post_id="1,2"]
</code></pre>
<h3>Requirements</h3>
<ul>
<li>WordPress: 6.6 or newer</li>
<li>PHP:
<ul>
<li>PHP 8.2+ required for development</li>
<li>PHP 8.1 may work for production builds when installed with <code>composer install --no-dev</code></li>
</ul>
</li>
</ul>
<h3>Languages</h3>
<p>OSEC supports multiple languages</p>
<h3>This Is a Fork</h3>
<p>OSEC is a fork of the GPL licensed plugin All-in-one-Event-Calendar by Timely. At it’s time a great plugin with a solid but unmaintainable codebase (not all required developer tools where opensourced).</p>
<p>If you love truly open source software and don’t mind to get your hands dirty you should join here. Free people need free software to manage and share events in a selfhosted manner.</p>
<h3>External services</h3>
<p>OSEC may connect to OpenStreetMap to render maps. If you using maps feature make sure you agree with <a href="https://operations.osmfoundation.org/policies/" rel="nofollow ugc">Terms of Service</a></p>
<p>OSEC may connect to OpenStreetMap Nominatim geocoding API. <a href="https://operations.osmfoundation.org/policies/nominatim/" rel="nofollow ugc">Terms of Service</a>.<br />
You may need to switch the servive on a heavy traffic site as Nominatim allows an <em>absolute maximum of 1 request per second</em>.</p>
<p>By default leaflet and leaflet-control-geocoder are loaded from unpkg.com. <a href="https://app.unpkg.com/policies@1.0.1" rel="nofollow ugc">Terms of Service</a>.</p>
<p>You can change using hooks: <code>osec_leaflet_library_alter</code>, <code>osec_leaflet_geocoder_library_alter</code>.</p>
<h3>Migration Notes</h3>
<p>Database structure is not fully compatible with All-in-One Event Calendar v2.3.4</p>
<p>Migration may be possible with manual effort</p>
<p>A standardized upgrade path may be developed if there is demand and contributions</p>
<p>See this <a href="https://github.com/digitaldonkey/open-source-event-calendar/wiki/migration-from-all%E2%80%90in%E2%80%90one%E2%80%90event%E2%80%90calendar" rel="nofollow ugc">wiki</a> for currently known information on migrating.</p>
<h3>Development & Support</h3>
<p>The principle behind this plugin is to be Open Source. Get in touch on <a href="https://github.com/digitaldonkey/open-source-event-calendar" rel="nofollow ugc">GitHub</a> to report issues, propose feature enhancements, and get general guidance for contributing.</p>
<p>Writing this fork was <a href="https://github.com/wp-plugins/all-in-one-event-calendar/compare/master...digitaldonkey:open-source-event-calendar:master" rel="nofollow ugc">a huge effort</a>.</p>
<p>Digitaldonkey believes everybody should be able to set up and manage public calendars.</p>
<p>If you are implementing this plugin for others you should support ongoing development with a <a href="https://www.paypal.com/donate/?hosted_button_id=ZNWEQRQNJBTE6" rel="nofollow ugc">donation</a> or <a href="https://github.com/digitaldonkey/open-source-event-calendar/issues" rel="nofollow ugc">contribution</a>.</p>
<p><a href="https://dri.es/solving-the-maker-taker-problem" rel="nofollow ugc">Be a maker</a>😀</p>
<p>Those wishing to contribute to the development of this project, please see the <a href="https://github.com/digitaldonkey/open-source-event-calendar/blob/master/.github/CONTRIBUTORS.md" rel="nofollow ugc">Development Guide</a> for more information.</p>


Open Source Event Calendar

An event calendar with native iCal / ICS import and export

WebCalendar vs Open Source Event Calendar