agenticdaisy

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.
Calendar Views & Display
<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>
Event Management
<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>
Import, Export & Sync
<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>
Collaboration & Permissions
<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>
SEO & Sharing
<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>
For Developers
<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>
Want Even More?
<a href="https://agenticdaisy.com/webcalendar/" rel="nofollow ugc">WebCalendar Pro</a> is a separate premium plugin that adds:
<ul>
<li>Appointment Booking — public scheduling with availability management</li>
<li>Google & Outlook Sync — two-way OAuth synchronization</li>
<li>Multisite Network Support — shared calendars across a WordPress network</li>
<li>White-Labeling — remove all WebCalendar branding</li>
<li>Priority Support — 24-hour response time SLA</li>
</ul>
The free version you’re using right now is fully functional with zero locked features. Pro adds capabilities that aren’t included here.
Technical Note: Database Architecture
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.
<h3>External Services</h3>
This plugin connects to the following third-party services:
<h4>Nager.Date API</h4>
Used for importing public holidays via WebCalendar > Holidays. 
* Endpoint: https://date.nager.at/api/v3/ 
* <a href="https://date.nager.at/LegalNotice" rel="nofollow ugc">Terms of Use</a> 
* <a href="https://date.nager.at/Privacy" rel="nofollow ugc">Privacy Policy</a>
<h4>Google Calendar Public Feeds</h4>
Alternative holiday source. Fetches public .ics files from Google. 
* Endpoint: https://calendar.google.com/calendar/ical/ 
* <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a> 
* <a href="https://policies.google.com/terms" rel="nofollow ugc">Google Terms of Service</a>
<h4>Thunderbird Holiday Calendars</h4>
Alternative holiday source via community-maintained .ics files. 
* Endpoint: https://www.thunderbird.net/media/caldata/ 
* <a href="https://www.mozilla.org/about/legal/terms/mozilla/" rel="nofollow ugc">Mozilla Terms of Use</a> 
* <a href="https://www.mozilla.org/privacy/" rel="nofollow ugc">Mozilla Privacy Policy</a>
<h4>Remote Calendar Sync (User-Configured)</h4>
When remote iCal subscriptions are configured, the plugin fetches .ics data from 
those URLs via HTTP GET. No user data is transmitted to these services.
<h4>OpenStreetMap / Nominatim</h4>
When a single event page has a location and the map provider is set to OpenStreetMap 
(the default), the plugin geocodes the address via the Nominatim API and displays a 
map using OpenStreetMap tile servers. The event location string is sent as a search 
query. No user personal data is transmitted. 
* Geocoding endpoint: https://nominatim.openstreetmap.org/search 
* Tile server: https://tile.openstreetmap.org/ 
* <a href="https://wiki.osmfoundation.org/wiki/Terms_of_Use" rel="nofollow ugc">OpenStreetMap Terms of Use</a> 
* <a href="https://operations.osmfoundation.org/policies/nominatim/" rel="nofollow ugc">Nominatim Usage Policy</a> 
* <a href="https://wiki.osmfoundation.org/wiki/Privacy_Policy" rel="nofollow ugc">OpenStreetMap Privacy Policy</a>
<h4>Google Maps Embed API</h4>
When the map provider is set to Google Maps in settings, single event pages display 
an embedded Google Map for the event location. The event location string and your 
Google Maps API key are sent to Google. No other user data is transmitted. 
* Endpoint: https://www.google.com/maps/embed/v1/place 
* <a href="https://cloud.google.com/maps-platform/terms" rel="nofollow ugc">Google Maps Platform Terms of Service</a> 
* <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a>
<h4>Add to Calendar Links</h4>
Single event pages include “Add to Calendar” buttons that generate links to Google 
Calendar, Outlook.com, and Yahoo Calendar. When a visitor clicks a button, the event 
title, date, time, location, and description are passed as URL parameters to the 
chosen service. No data is sent until the visitor clicks. 
* 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> 
* 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> 
* 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>
<h4>Social Sharing Links</h4>
Single event pages include social sharing buttons for Facebook, X (Twitter), and 
LinkedIn. When a visitor clicks a button, the event page URL and title are passed as 
URL parameters to the chosen service. No data is sent until the visitor clicks. 
* 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> 
* 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> 
* 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>
<h3>Development & Source Code</h3>
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.
What ships in this zip:
<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>
Rebuilding the compiled assets from source:
Prerequisites: PHP 8.2 or higher with Composer 2, Node.js 20 or higher with npm 10.
<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>
The compiled output in <code>build/</code> is byte-reproducible from the matching <code>src/</code> at the same version using this toolchain.

WebCalendar

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

hoernerfranz

Ever thought about to use your (remote) CalDav Calendar(s) as an automatic data source for your favourite WP Calendar Plugin ? 
Searched for a Plugin that would provide this functionality in the WP Plugins Directory and found nothing useful ? 
Well, in case of ‘Yes’ to both questions, this is for You 🙂 . 
Just read the whole story at https://hoernerfranzracing.de/werner/kde-linux-web/wp-caldav2ics to check out if this will fit your needs… 
And yes, Calendar(s) is correct from Version 1.1.0 – you are no longer limited to just ONE Calendar Source !

WP-CalDav2ICS

Automatically create ICS File from CalDav Calendar

WebCalendar vs WP-CalDav2ICS