Title: SDAweb Calendar Sync for Google Calendar Author: rstake Published: May 15, 2026 Last modified: June 13, 2026 --- Search plugins ![](https://ps.w.org/sdaweb-gcal-sync/assets/icon.svg?rev=3533428) # SDAweb Calendar Sync for Google Calendar By [rstake](https://profiles.wordpress.org/rstake/) [Download](https://downloads.wordpress.org/plugin/sdaweb-gcal-sync.0.21.4.zip) * [Details](https://co.wordpress.org/plugins/sdaweb-gcal-sync/#description) * [Reviews](https://co.wordpress.org/plugins/sdaweb-gcal-sync/#reviews) * [Installation](https://co.wordpress.org/plugins/sdaweb-gcal-sync/#installation) * [Development](https://co.wordpress.org/plugins/sdaweb-gcal-sync/#developers) [Support](https://wordpress.org/support/plugin/sdaweb-gcal-sync/) ## Description SDAweb Calendar Sync turns any Google Calendar into a polished, on-brand events display on your WordPress site — without duplicate data entry. Keep scheduling in Google Calendar the way you already do; the plugin pulls those events in and keeps your site in sync automatically. It’s for anyone who already runs their events in Google Calendar and wants them to look like a native part of their site instead of an embedded iframe — businesses, teams, venues, clubs, communities, and organisations of every kind. Insert a calendar with a Gutenberg block, a shortcode, or a classic widget. All three share one render pipeline, so the output is identical however you add it. #### Six ways to show your calendar * **List / Agenda** — chronological, optionally grouped by day, week, or month * **Month grid** — classic 7×6 calendar with multi-day event ribbons spanning across cells, today highlight (cell or whole-column style), optional ISO 8601 week-number column, and per-feed pastel chips * **Card grid** — upcoming events as styled cards, responsive * **Week** — 7 day columns, today highlighted * **Day** — single-day agenda * **Mini-month** — compact dot-density grid for sidebars and widgets, with a tap- to-expand event panel showing today + next upcoming events and a “Load more” button Switch between views with one setting, or expose a visitor-facing view-toggle pill so visitors can switch themselves. Under the hood every view shares the same data layer, the same CSS-variable system, and the same accessibility baseline. #### Smart UX out of the box * **Hover popover on event chips** (Month, Week, Mini) — a floating card with date, time, location, calendar, recurrence summary, and a click-through link, so visitors get the full event detail without leaving the page. Desktop hover + keyboard focus only; touch users keep direct click-through. * **Mobile auto-degrade Month Mini** — below ~600px the full grid is replaced by the compact Mini-month view, so phone visitors get a clean, tappable calendar with no extra work from you. One wrapper, two layouts, no JS swap. * **ICS subscribe dropdown** — one tap to add your events to a visitor’s own calendar: Google Calendar (web), Apple Calendar / Outlook (webcal), Android Google Calendar app (intent), and Copy-link with toast confirmation. Mobile becomes a bottom sheet. * **Live search** + **jump-to-date picker** — optional chrome controls so visitors can filter or navigate quickly. * **Multi-day event ribbons** — week-spanning bars with arrow indicators when an event continues beyond the visible row. * **Recurring event indicator** — small ↻ icon with a plain-language cadence summary in the tooltip (“Repeats weekly until 31 December 2026”). * **Per-display locale override** — render a calendar in a specific language (e. g. nb_NO) even when the site language differs, so you can run a localized calendar on a site that’s in another language. #### Two authentication paths * **API key** — for calendars marked “Make available to public” in Google Calendar. One field, paste, done. * **Service Account JSON** — for **private** calendars without per-user OAuth. Upload the JSON, share the calendar with the service-account email, you’re set. Credentials are encrypted at rest using a key derived from your site’s authentication salt. They are never echoed back into the admin UI — only the masked value and ( for service accounts) the public service-account email are shown. #### Theme-aware out of the box The plugin reads your active theme’s `theme.json` color palette and uses your `primary`,` accent`, `foreground`, and `background` colors automatically. Per-display overrides let you set custom primary, accent, today-highlight, and link colors and force light/ dark mode without touching code. Every design token is exposed as a CSS custom property so a developer can fully restyle the calendar from their theme stylesheet. #### Five built-in theme presets One-click coordinated colour bundles: **Default** (clean blue), **Warm earth** ( cream + deep red), **High contrast** (solid black on white for AAA-stricter sites),** Forest** (deep green), **Sunset** (warm coral + amber). #### Accessibility built in WCAG 2.2 AA baseline with several AAA touches: * Live contrast warnings on every colour picker — the admin UI shows the WCAG ratio against both light and dark surfaces with pass/fail markers as you choose colours * Automatic high-contrast overlay via `prefers-contrast: more` * Focus-visible halo: a 4px white ring behind the primary outline so focus stays visible against any chip background * `prefers-reduced-motion` honored everywhere * ARIA roles and labels on the month grid, navigation, popovers, and view-toggle * Semantic HTML throughout * RTL-aware via CSS logical properties * Tabular numerals for day numbers and time labels so single- and double-digit values don’t drift #### Built for the WordPress.org standard * Block editor first-class — server-side rendered, ServerSideRender preview, all the standard `InspectorControls` * Shortcode and classic widget on the same render pipeline * No bundled core libraries (no jQuery on front-end, no Guzzle, no Carbon, no Monolog) * No third-party authentication relay — your credentials only ever talk directly to googleapis.com * Translation ready via translate.wordpress.org once the plugin is published and indexed (no bundled `.po`/`.mo` — WordPress auto-loads locale files into `wp- content/languages/plugins/` per the WP Plugin Handbook), plurals via `_n()`, JS strings via `wp_localize_script` * Free and GPLv2 #### For developers Extension hooks are documented in `docs/hooks.md` inside the plugin folder. The first-release set includes filters for event data, event URLs, query args, cache TTL, render output, palette resolution, plus actions for refresh and uninstall lifecycle. ### Third-Party Services This plugin connects to the Google Calendar API to retrieve events from calendars you configure. * Service: Google Calendar API v3 * Website: https://developers.google.com/calendar * Terms of Service: https://developers.google.com/terms * Privacy Policy: https://policies.google.com/privacy Data sent: the calendar ID(s) you configure, plus either your API key or a JSON Web Token signed with your service account credentials. Event data is returned to your server and cached locally as WordPress transients. No event data is sent to any third party. The ICS subscribe feature, when enabled, links visitors directly to Google’s public iCal feed (`calendar.google.com/calendar/ical/.../public/basic.ics`) — the plugin does not proxy or store that data. ## Blocks This plugin provides 1 block. * SDAweb Calendar Display events from one or more Google Calendars. Choose a saved display or configure inline. ## Installation 1. Upload the plugin to your `/wp-content/plugins/` directory, or install it from the Plugins screen in WordPress. 2. Activate the plugin. 3. Go to **Settings SDAweb Calendar Sync** to add your first calendar. 4. Choose API key (public calendars) or Service Account (private calendars), follow the in-app setup guide, save. 5. Create a display, choose a view, and copy its shortcode — or insert the **SDAweb Calendar** block in a page. ## FAQ ### Do I need a Google account to use this plugin? You need a Google Cloud project to generate either an API key (for public calendars) or a service account (for private calendars). The plugin’s Help tab walks you through both setups in 7–8 steps each. Setup is one-time per site. ### Does this plugin send my data anywhere other than Google? No. Calendar data is fetched directly from `googleapis.com` using the Google Calendar API. The plugin does not contact any SDAweb-controlled servers, analytics endpoints, or third-party relays. There is no telemetry. ### Can I display a private (non-public) calendar? Yes. Use the Service Account authentication option. The plugin shows you the service account email; share your private calendar with that email in Google Calendar’s sharing settings, and the plugin can read it. ### How often does the plugin refresh events? A WP-Cron job refreshes registered calendars in the background every 15 minutes. Cache lifetime is configurable upward in the plugin settings (15 minutes is the enforced minimum). You can also click “Refresh now” on any calendar in the admin to fetch immediately. ### Does it work with caching plugins? Yes — the calendar HTML is part of the page output, so any page-cache plugin caches it like any other content. The cache will refresh on its own schedule. If you need immediate refresh after a calendar change, purge the page cache. ### Can I add multiple calendars to one display? Yes. Each display picks one or more registered calendars and merges them. Events are color-coded by calendar. A multi-feed legend strip can be enabled above the events; chips can be styled solid (single-feed) or pastel (multi-feed legibility). ### Will it work with my theme? The plugin reads your active theme’s `theme.json` color palette automatically, so calendar colors match the site by default with zero configuration. If you use a classic theme without `theme.json` (or want to override), every color is exposed as a CSS variable that you can override from your theme stylesheet. Five built-in theme presets give you coordinated palettes with one click. ### Is the plugin accessible? Yes — built-in. WCAG 2.2 AA baseline includes `prefers-reduced-motion` and `prefers- contrast: more` support, `:focus-visible` outlines with a white halo (visible on any background), ARIA labelling on the month grid, navigation, popovers, and view- toggle, semantic HTML throughout, RTL-aware via CSS logical properties, and live contrast warnings in the colour-picker UI as you choose values. ### Can I show the calendar in a different language than the rest of the site? Yes. Each display has an optional Locale override field — set it to `nb_NO`, `sv_SE`, etc. and that calendar renders weekday names, month names, and built-in labels in that language regardless of the site’s language. Useful when an English site hosts Norwegian-audience content. ### Where are the extension hooks documented? In `docs/hooks.md` inside the plugin folder. The plugin commits to keeping documented hooks stable within a major version. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “SDAweb Calendar Sync for Google Calendar” is open source software. The following people have contributed to this plugin. Contributors * [ rstake ](https://profiles.wordpress.org/rstake/) * [ sdaweb ](https://profiles.wordpress.org/sdaweb/) “SDAweb Calendar Sync for Google Calendar” has been translated into 1 locale. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/sdaweb-gcal-sync/contributors) for their contributions. [Translate “SDAweb Calendar Sync for Google Calendar” into your language.](https://translate.wordpress.org/projects/wp-plugins/sdaweb-gcal-sync) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/sdaweb-gcal-sync/), check out the [SVN repository](https://plugins.svn.wordpress.org/sdaweb-gcal-sync/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/sdaweb-gcal-sync/) by [RSS](https://plugins.trac.wordpress.org/log/sdaweb-gcal-sync/?limit=100&mode=stop_on_copy&format=rss). ## Changelog The most recent releases are listed here. The complete history is in docs/CHANGELOG. md bundled with the plugin. #### 0.21.4 * Fixed: the Upcoming view could show far fewer events than “Maximum events to show” (e.g. only 2 of 6) when the calendar had one or more events earlier the same day. The general “Max events” cap was applied _before_ the Upcoming view drops past events, so events earlier today consumed the cap and pushed the upcoming ones out of the list. The cap no longer pre-truncates the Upcoming list — “Maximum events to show” is now applied after past events are removed, so the view reliably shows the configured number of upcoming events (as long as the calendar has them). Front-end fix; affects both the shortcode/block render and the instant view-swap. #### 0.21.3 * Improved: the Displays editor’s Live preview now shows a “Showing N events” count of what it actually rendered, updated as you switch preview views. Because the preview uses the same renderer as the public site, the number is exactly what visitors see — so you can confirm at a glance how many events a display will show, instead of loading the front-end to check. Admin-only; no change to the calendar front-end. #### 0.21.2 * Improved: clearer Upcoming view options in the Displays editor. The “Event time size” control now greys out with an inline “needs Show meta line enabled” note when the time/All-day line is turned off — so it’s obvious the control depends on that toggle (same pattern already used for Title size). The event-name controls are renamed “Event name size” / “Event name weight” to clearly distinguish them from “Event time size”. Admin-only; no change to the calendar front-end. #### 0.21.1 * Improved: the Displays editor’s view-filter buttons now fold their section count into the button’s accessible label, so screen-reader users hear it (e.g. “Show only List settings (3 sections)”) instead of only sighted users seeing the badge— with correct singular/plural. The “All” button’s tooltip now states the total. Admin-only; no change to the calendar front-end. #### 0.21.0 * Improved: the Displays editor’s per-section view chips are replaced by a single accessible filter bar at the top of the form. Clicking a view (Upcoming / List/ Card / Month / Mini) now truly hides the settings that don’t apply to it, instead of just dimming them. The previous dimming was invisible to screen-reader users and left the irrelevant sections in place; the new bar shows a count per view, a live “Showing N of M sections” status, and remembers your choice per display. Admin-only and purely visual — every field still saves even while a filter is active, and a filter is automatically cleared if a section has a validation error so it can never be hidden. No change to the calendar front-end. * Improved: the filter bar is a full ARIA toolbar — one tab stop with arrow-key( and Home/End) navigation between buttons; each view button has a tooltip explaining its count (sections specific to that view); and a saved filter is now applied before the form paints, so returning to a filtered display no longer briefly flashes all sections before collapsing. With JavaScript disabled, every section stays visible. * Fixed: an instant view-swap could load the calendar chrome (view labels, month name, weekday names) in the wrong language when triggered by a logged-in user whose profile language differs from the site language. The swap’s REST render ran in the user’s locale; it now renders in the site locale to match the surrounding page, while a display’s own explicit locale override still applies. Logged-out visitors were never affected. #### 0.20.0 * Improved: the single “Event chip style” setting is now two clearer, independent settings — “List view: event row style” (Linear / Boxed / Elevated) and “Month view: event chip style” (Solid / Pastel). Previously one control mixed both views and you could only pick one; now you can style the List and Month views separately on the same display, which matters when visitors can switch views. The old “Card” List option is renamed “Elevated” so it no longer reads like the separate Card grid view. Existing displays, saved blocks, and shortcodes are migrated automatically and look exactly the same. (The Week, Day, Card grid, Mini-month, and Upcoming views are unaffected by these settings, as before — see Help “Event styles: which views they affect”.) * Improved: the Displays Outbound links section is split into clearly-scoped subsections( Event links / Footer “See all” link / Upcoming title-row link / Mini-month link), each tagged with the views it affects, so the view-filter chips dim the ones that don’t apply. The footer-link toggle now names all three views it covers ( List, Upcoming, Card), and the Upcoming view warns when both its title-row link and footer link are on under “Auto” placement (which shows two “See all” links) so you can collapse them with the Link placement control. Admin-only clarity — no change to the rendered output. #### 0.19.1 * Fixed: after an instant view-swap into the List view (e.g. clicking the “List” toggle from the Month grid), the week/day section headings lost their pill styling and the events lost their colour accent bars until the page was hard-refreshed. The swap replaced the calendar’s inner markup but only rewrote the view modifier class on the wrapper, so List’s layout classes (`heading-position-*`, `chip-style-*`) were never applied to the persistent root and the matching CSS stopped taking effect. The swap now re-applies the wrapper’s full class list from the server, so a swapped view looks identical to a full page load. Affects every view-to- view swap, not just MonthList. * Fixed: on iOS / touch devices a stray focus box (e.g. a red rectangle around the “Uke 24” heading) could appear around a view’s first section heading after an instant view-swap. The 0.19.0 fix only suppressed this for the List view on desktop; iOS Safari treats the script-moved focus as keyboard focus, so the box still drew on touch and in other views (Card / Week / Month). The heading focus is now flagged so its ring is suppressed regardless of browser or view — the accessibility focus-move and screen-reader announcement are unchanged. * Fixed: in the Month / Week / Day / Mini views, clicking the Previous / Today / Next arrows could switch the visitor to a different view (tab) instead of just changing the period. The navigation links didn’t pin the current view, so they inherited a stale or missing view from the page URL (after a view-swap the previous view was still in the URL when the links were built). The arrows now always keep you on the current view — only the month/week/day changes. Most visible on mobile, where the Month view shows its compact fallback. #### 0.19.0 * Improved: the List view’s week/day section headings (e.g. “UKE 24”) now read as confident, editorial section dividers — slightly larger with more open letter- spacing and breathing room. Also fixes a stray focus outline that could appear as an empty box around the first heading after an instant view-swap: the programmatic focus that swap.js moves to the new content no longer shows the theme’s default outline, while real keyboard focus keeps a clean, visible ring. #### 0.18.1 * New: the Upcoming “Today / Tomorrow” pill can now have its own colour, independent of the event colour (Displays Upcoming view options “Today / Tomorrow pill color”). Leave it empty to keep the previous behaviour (the pill follows the event colour). The pill’s text colour (light or dark) is chosen automatically to stay legible (WCAG AA) on whatever colour you pick. #### 0.18.0 * New: two more per-Display options for the Upcoming view, both opt-in so existing displays are unchanged. (1) “Event time size” — scale the time / All-day line under each event (Small 11px default / Medium 13px / Large 15px); the event name and date column are unaffected. (2) “Date badge color” — give the filled date badge its own colour, independent of the event colour (leave empty to keep following the event colour); it still auto-darkens to keep white text legible. Also adds a short hint under “Maximum events to show” pointing to the “Days forward” date window for when fewer events appear than expected. #### 0.17.0 * New: three additive per-Display options for the Upcoming view (Displays Upcoming view options), all opt-in so existing displays render exactly as before. (1) “ Date badge size” — Compact / Standard / Large scaling for the filled date badge( applies only when “List date style” is “Filled date badge”). (2) “Show Today / Tomorrow labels” — a small pill on events happening today or tomorrow, resolved in the site timezone, reusing the existing Today/Tomorrow labels. (3) “Group events” — optional day or week headings inserted through the list (ISO-8601 week). All three apply identically on the initial page load and after an instant view- swap. #### 0.16.4 * New: admin control for the event-text size in the Upcoming view (“Event text size”: Small 13px / Medium 15px / Large 17px / X-Large 20px), plus an optional“ Event text weight” (400–700). Both live in Displays Upcoming view options. Defaults are unchanged (Small / Normal), so existing displays render exactly as before. Applies identically on the initial page load and after an instant view-swap. #### 0.16.3 * Fixed: the 0.16.2 view-toggle date fix did not reach the instant-view-swap (REST) render used on mobile, so the garbage 19th-century focus date persisted there. Two causes: (1) the out-of-range date guard now lives in the single shared anchor resolver, so the grid, the Previous/Today/Next nav and the view-toggle links are all driven by the same validated date on both the full-page and the REST render — no per-path date logic; (2) the render cache is now keyed on the plugin version, so an upgrade no longer serves HTML cached by the previous version. Note: clearing the calendar render cache once after updating flushes any partial still cached by 0.16.1/0.16.2. #### 0.16.2 * Fixed: on a calendar with no explicit date (the default render), the view-toggle links (List / Month / Cards / Week / Day) baked a corrupted/uninitialised focus date into their href — sending a view switch to a garbage 19th-century date with no events, after which every view stayed stuck on it. The grid and the Previous/ Today/Next links were always correct; only the toggles were affected, because they preserved whatever focus the page URL carried instead of using the date the grid resolved to. The toggles now use the single resolved anchor (so switching view keeps the date you’re looking at), and an out-of-range guard makes a far- past/far-future focus impossible regardless of source. #### 0.16.1 * New: per-display “Link event titles” toggle (Outbound links Event link behaviour), on by default. When on, behaviour is unchanged — an event title links to a tagged“ Info:” URL when its description has one, otherwise to the Google Calendar event. Turn it off to render event titles as plain text with no link anywhere (the hover popover still shows the event details). Useful when the Google Calendar event page isn’t helpful to visitors — e.g. a public calendar whose event pages send logged-out visitors to Google’s product page. #### 0.16.0 * No user-facing change — internal hardening so a new per-Display option can no longer work in the admin preview yet silently vanish on the front-end. A single field registry (new `Display_Schema` class) now drives the admin form, the block/ shortcode defaults and sanitizer, the save handler, and the renderer, and collapses ~600 lines of duplicated field plumbing. #### 0.15.1 * Fixed: the per-display “Chip text color” setting now applies on the front-end and the view-swap, not only in the admin preview (it was being stripped by `shortcode_atts()` because `chip_text_mode` wasn’t a declared default). * Security: the API key is now redacted from PHP error-log entries. * Housekeeping: uninstall removes more leftover options, including credential-bearing config backups. #### 0.15.0 * Fixed: long event titles (and locations) with no spaces — e.g. a compound word containing a slash — overflowed the right edge of the box in the Cards view instead of wrapping. Card text now breaks long tokens to stay inside the card. #### 0.14.6 * New: “Link placement” control for the Upcoming view — put the “See all” link above the list, or at the bottom left / center / right, from a single per-Display dropdown. The link’s URL, label, and style come from the existing Footer link fields. The default “Auto” keeps the previous behaviour unchanged, so existing displays are byte-identical until you opt in. #### 0.14.5 * Fixed: the “Filled date badge” list style added in 0.14.4 showed only in the admin Live preview, never on the front-end. The shortcode/block config goes through` shortcode_atts()`, which drops any key not declared in the shortcode defaults— and `list_date_style` wasn’t declared there, so the saved value was stripped before it reached the renderer and the Upcoming view fell back to plain. The same applied to the instant-view-swap fragment, which renders through the identical shortcode pipeline. Registered `list_date_style` in the shortcode defaults and sanitizer, so the badge now renders on the front-end in both the initial page load and after a view swap. #### 0.14.4 * New: Added an optional filled date-badge style for the list/Upcoming view, selectable per Display (“List date style” “Filled date badge”). The badge color is taken from the display’s event color override (or a default blue) and auto-darkens to keep its white text at WCAG AA contrast (≥ 4.5:1) no matter which accent you choose. The default “Plain text” style is unchanged. #### 0.14.3 * Fixed: a tagged `Info:` link did not work on touch devices (tablets/iPads). On a touch device the event-hover popover opens on tap and deliberately suppresses the chip’s own link, so the popover’s title link is the only reachable navigation— but that link still pointed at the Google Calendar event page instead of the admin-chosen `Info:` URL. It now uses the same resolved headline URL as every other surface, so tapping an event on a pad opens your linked page. The popover title link also honours the display’s “Open custom links in” / “Open event links in” setting (previously always a new tab) and shows the info icon, matching the chips and the other popovers. Desktop (hover) was unaffected because the chip’s own link handled the click there. #### 0.14.2 * Improvement: The Mini-month day popover and the Month “+N more” overflow popover now respect the display’s “Open event links in” / “Open custom links in” settings, matching the other views. Previously the mini day popover always opened links in a new tab and the month overflow popover always in the same window, regardless of the setting. #### 0.14.1 * Improvement: The info icon for events with a tagged link now also appears in the JavaScript-rendered surfaces — the Mini-month agenda panel and day popover, and the Month “+N more” overflow popover (previously only the link itself swapped there). The icon is now shown consistently across every view and surface. #### 0.14.0 * New: Link an event to a page of your choosing. Add a line beginning with `Info:` followed by a URL to an event’s Google Calendar description (e.g. `Info: https:// example.com/page`) and the event title links to that page instead of the Google Calendar event — with a small, theme-aware info icon beside the title as a cue. The `Info:` line is hidden from the description shown on your site, Google’s own event page remains reachable from the hover popover, and recurring events carry the link to every occurrence. Works across all six views; the icon shows in List, Card, Day, Week, Upcoming and Month. See Help “Link an event to your own page”. * New: Per-display toggle “Use a tagged link from the event description” (Outbound links section), on by default, plus a separate “Open custom links in” (same window/ new tab) control — independent of the Google-link setting, so your own pages can open in the same window while Google Calendar links open in a new tab. Defaults to same window. * Dev: New filter `sdaweb_gcal_link_marker` to change the marker token (default` Info:`) for other locales/conventions. ## Meta * Version **0.21.4** * Last updated **5 days ago** * Active installations **50+** * WordPress version ** 6.5 or higher ** * Tested up to **7.0** * PHP version ** 7.4 or higher ** * Languages * [English (US)](https://wordpress.org/plugins/sdaweb-gcal-sync/) and [Norwegian (Bokmål)](https://nb.wordpress.org/plugins/sdaweb-gcal-sync/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/sdaweb-gcal-sync) * Tags * [agenda](https://co.wordpress.org/plugins/tags/agenda/)[calendar](https://co.wordpress.org/plugins/tags/calendar/) [events](https://co.wordpress.org/plugins/tags/events/)[google calendar](https://co.wordpress.org/plugins/tags/google-calendar/) [schedule](https://co.wordpress.org/plugins/tags/schedule/) * [Advanced View](https://co.wordpress.org/plugins/sdaweb-gcal-sync/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/sdaweb-gcal-sync/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/sdaweb-gcal-sync/reviews/) ## Contributors * [ rstake ](https://profiles.wordpress.org/rstake/) * [ sdaweb ](https://profiles.wordpress.org/sdaweb/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/sdaweb-gcal-sync/)