Belltime Events Calendar is an events calendar for sites where a wrong time has a\ncost \u2014 venues, studios, course providers, conference organisers. It does three\nthings carefully and leaves the rest alone.<\/p>\n\n
Recurring events, in full, in the free plugin.<\/strong> Not just \"every week\": intervals,\noccurrence counts, end dates, ordinal weekdays such as the second Tuesday or the\nlast Friday, days of the month counted from either end, months of the year,\nset positions, explicit extra dates, and cancelled dates. If your quiz night is\nevery other Tuesday and your class is the first Saturday of the month, the plugin\nexpresses both and produces the right dates for them.<\/p>\n\n Occurrences are never database rows.<\/strong> A weekly class running for two years is one\nevent with one rule, not 104 posts in your database, your sitemap and every other\nplugin's queries. The dates are worked out when a page is drawn. No scheduled job\ngenerates anything, and there is nothing to reconcile when you edit a series.\nCancelling or moving a single occurrence records only that exception \u2014 the rest of\nthe series keeps its dates and its links.<\/p>\n\n Times that stay right.<\/strong> Every event stores a wall-clock time, a length, and the\nname of its timezone. That combination is what keeps a 19:00 event at 19:00 after\nthe clocks change, keeps a two-hour event two hours long across a daylight-saving\ntransition, and lets a touring show carry the local time of each city it plays. When\nthe timezone database is updated, the derived values are recalculated rather than\nleft to drift.<\/p>\n\n A separate paid add-on adds incoming synchronisation: subscribing to .ics feeds from\nGoogle Calendar, Outlook and Microsoft 365, Apple iCloud, Nextcloud, Teamup and\nanything else that speaks iCalendar, with several calendars at once and a panel\nshowing when each last synced and what failed. It is not required, and\nnothing here is limited or disabled without it.<\/p>\n\n This plugin mentions the add-on only to administrators, and only on its own screens: a\n\"Sync from other calendars\" tab and a dismissible line on its settings screen, a line\nin the \"Get started\" box while the events list is empty and a button on the list once\nit has events, a dismissible line when adding an event once one already exists, and a\nlink in its own row on the Plugins screen. Nothing appears in the block editor. None of\nthem is a site-wide notice or a dashboard widget, none opens by itself, none shows a\nprice, and all of them disappear once an add-on is active. Details are on the plugin's\nhome page, which is the Plugin URI on this listing.<\/p>\n\n This plugin does not use any external services.<\/strong> It makes no outbound network\nrequests of any kind: no licence check, no update check, no usage statistics, no\ntelemetry, no error reporting, and no request to any third party. Nothing about your\nsite, your events or your visitors is transmitted anywhere by this plugin.<\/p>\n\n The outgoing iCal feed this plugin publishes is served from your own site. When a\nvisitor subscribes to it, their calendar application requests it from your server\ndirectly; no third party is involved and no request is made from your site to anyone.<\/p>\n\n The separate paid add-on does contact a licence and update service, and discloses that\nin its own documentation. That add-on is not this plugin and is not distributed here.<\/p>\n\n\n Add the Belltime Events Calendar<\/strong> block to a page \u2014 it is under Widgets<\/em> in the block\ninserter \u2014 or use the shortcode:<\/p>\n\n [belltime_events]<\/p>\n\n The shortcode takes optional attributes:<\/p>\n\n [belltime_events view=\"month\"]\n[belltime_events view=\"list\" limit=\"5\" days=\"90\" category=\"concerts\"]<\/p>\n\n Visitors can subscribe to your calendar at If your site's PHP or WordPress version is older than this plugin requires, it will\nnot load and will tell you so in an admin notice. It will not take your site down.<\/p>\n\n\n No. One event carries one recurrence rule and the dates are calculated when a page is\ndrawn. Only exceptions \u2014 a cancelled or moved occurrence \u2014 are stored, and there is\none record per exception rather than per occurrence.<\/p><\/dd>\n FREQ (daily, weekly, monthly, yearly), INTERVAL, COUNT, UNTIL, WKST, BYDAY including\nordinals such as 2TU and -1FR, BYMONTHDAY including negative values, BYMONTH,\nBYSETPOS, plus EXDATE and RDATE. If the plugin meets a rule it cannot expand, it shows\nthe base occurrence and says so in an admin notice rather than silently producing\nwrong dates.<\/p><\/dd>\n Yes. The site timezone is the default and any event can override it. Useful for\ntouring productions, online courses and organisations operating in more than one\ncountry.<\/p><\/dd>\n It stays two hours long. The plugin stores a duration rather than an end time, which\nis what keeps the length correct across a clock change in either direction.<\/p><\/dd>\n Both. There is a block for the block editor and a shortcode for classic editors,\nwidget areas, page builders and theme templates. Both take the same options and\nproduce the same output. The plugin's settings screen shows the shortcode in its\n\"Get started\" box, so you can copy it without leaving the page. Its attributes are\n view, It should cost nothing on pages that do not contain a calendar. Seven callbacks are\nregistered \u2014 two for the calendar feed ( They stay. Deleting the plugin removes its options and its cached values, and leaves\nyour events in the database. Removing them as well is a checkbox you have to tick\ndeliberately before deleting, because a deletion that cannot be undone should never\nbe the default.<\/p><\/dd>\n Not in this plugin. Incoming synchronisation is in the separate paid add-on described\nin the Description section. This plugin publishes an outgoing feed but does not read\nanyone else's.<\/p><\/dd>\n That is the cache, and it is worth knowing about rather than working around. The month\nview marks today while the page is built on your server. A full-page cache then serves\nthat same HTML to everyone until it expires, so if the page was built yesterday, the\nhighlight is on yesterday.<\/p>\n\n Nothing else in the calendar is affected: dates, times and the order of events are all\nproperties of the events themselves, and they stay right. Only the \"today\" highlight\ndepends on when the page was rendered.<\/p>\n\n We have deliberately not fixed this with JavaScript. The frontend of this plugin ships\nnone at all, which is what lets it work inside caches, AMP-style output and strict\ncontent security policies without special cases, and a highlight is not worth giving\nthat up. If it matters on your site, exclude the page from your cache, or set the cache\nlifetime to expire nightly.<\/p><\/dd>\n\n<\/dl>\n\n\nWhat it includes<\/h4>\n\n
\n
What it deliberately does not do<\/h4>\n\n
\n
Pro<\/h4>\n\n
External services<\/h3>\n\n
\n
Europe\/Copenhagen<\/code> rather than a fixed offset such as UTC+1<\/code>. A fixed offset\ndoes not know when your country changes its clocks, and every event will be an hour\nout for half the year. This is the single most common cause of wrong event times on\nWordPress sites, and it is not specific to this plugin.<\/li>\n\/belltime-calendar.ics<\/code>.<\/p><\/li>\n<\/ol>\n\n\n
Does it create a post for every occurrence of a repeating event?<\/h3><\/dt>\n
Which recurrence rules are supported?<\/h3><\/dt>\n
Can each event have its own timezone?<\/h3><\/dt>\n
What happens to a two-hour event that crosses a daylight-saving change?<\/h3><\/dt>\n
Does it work with the block editor and with page builders?<\/h3><\/dt>\n
limit<\/code>, days<\/code>, category<\/code> and month<\/code>, and they are documented here.<\/p><\/dd>\nWill it slow my site down?<\/h3><\/dt>\n
template_redirect<\/code>, and redirect_canonical<\/code> so\nthe feed address is not redirected), one on pre_get_posts<\/code> for the events archive, two\non the content filters, and two on the date filters so an event shows its own date\nrather than the day it was published \u2014 and every one of them returns on its first line\nwhen the request is not about events. No scheduled task is\nregistered, no database table is created, and exactly two small options are autoloaded.\nThis is worth verifying yourself with Query Monitor rather than taking on trust.<\/p><\/dd>\nWhat happens to my events if I delete the plugin?<\/h3><\/dt>\n
Does it import from Google Calendar or Outlook?<\/h3><\/dt>\n
I use a page cache, and the month grid highlights the wrong day<\/h3><\/dt>\n
0.1.0<\/h4>\n\n
\n