SDAweb Calendar Sync for Google Calendar

Changelog

The most recent releases are listed here. The complete history is in
docs/CHANGELOG.md bundled with the plugin.

0.8.6

• Fix: Service-account token-exchange success no longer writes to the PHP error log unconditionally. The success path is now gated on WP_DEBUG; on busy sites this was logging one line every ~55 minutes even when everything was working correctly. Token-exchange failures and API errors continue to log unconditionally so real problems are always surfaced.
• Fix: Upgrade notice for 0.8.3 in readme.txt exceeded WordPress.org’s 300-character limit (Plugin Check upgrade_notice_limit warning). No code change.

0.8.5

• New: Delete button on each row in Tools → Backups. Snapshots could previously only be removed by capturing three new ones to push them out of the retention window — fine for routine pruning, awkward when a single test snapshot wanted to go. The Delete button now removes one specific snapshot immediately (confirm dialog first; record is gone from the sdaweb_gcal_backups option). Frees a retention slot so the next pre-import/manual snapshot won’t prune a newer one to make room.

0.8.4

• Fix: Solid Month chips lost their auto-resolved text color on hover. The general .sdaweb-gcal a:hover rule in front.css set a hover color that cascaded into the chip’s <a> because the more specific .sdaweb-gcal-month__event a:hover rule only set text-decoration — same specificity, no color reset, so the general rule’s color property won by cascade. Result: a chip whose Auto mode picked dark text correctly would flip to the link/accent color on hover, often dropping back below the WCAG threshold the Auto mode was protecting. Fix pins the hover color to inherit and adds a subtle text-underline-offset: 2px for breathing room. Week/Day chips deliberately keep their primary-color hover (different chip design — surface backgrounds, hover affordance comes from the color change).

0.8.3

• New: Solid chip text color option on the display edit screen (Appearance → Event chip style → Solid chip text color). Three modes: Auto (default) computes the WCAG relative-luminance contrast for white vs dark text against each chip background and picks the higher-contrast side; Always light (white) preserves the pre-0.8.3 behaviour; Always dark forces dark text. Fixes a long-standing readability issue where Solid chips with mid-luminance feed colors (greens like #16a34a, yellows, mints) rendered as white text on a too-light background and the title “faded into” the chip in the tiny month-grid footprint. Existing displays render unchanged on first load (Auto picks white for the same dark reds/blues/teals that white was already being used on); only chips whose feed color previously failed AA against white will switch to dark text.

0.8.2

• New: Upcoming view exposes three new per-display title appearance controls — Title size (Small / Medium / Large / X-Large), Title weight (Normal / Medium / Semi-bold / Bold), and an Uppercase title toggle. Useful when the surrounding container’s headings (sidebar widget titles, footer column headers) use a different weight/case than the plugin’s default 15px / 500, so the “Fra kalenderen”-style title can be tuned to blend in without site CSS overrides. Existing displays render unchanged — defaults match the previous hard-coded values.
• Change: The Upcoming view’s “See all →” link now always opens in the same window, regardless of the display’s Link target setting. The link points to the site’s own calendar page; opening a same-site link in a new tab is a UX anti-pattern (breaks the back button, loses navigation context). Per-event URLs (typically off-site) continue to honour the Link target setting.

0.8.1

• Fix: View-toggle / focus-date / “+N more” / date-jump URLs are now scoped to the calendar instance whose control was used — they no longer bleed into every other calendar on the page. Previously, switching the main calendar to Month or Day view also flipped any other calendar instance on the page (footer widgets, sidebar instances) into the same view. A footer “Upcoming” widget on the same page as a Month-view calendar would render as a cramped Month grid in the narrow footer column, and looked broken. Same root issue for ?sdaweb_gcal_focus= — every calendar on the page jumped to the same date. Fix: every navigation URL now carries sdaweb_gcal_id=<display-slug> and the renderer ignores the override unless the URL’s id matches the current display.

0.8.0

• New: Month-view “+N more” indicator is now interactive (was a non-clickable <li> — a real a11y gap; keyboard users and screen readers couldn’t reach it). New per-display option Day overflow (“+N more”) under “Month view options” with two modes: popover (default) opens an in-place panel listing the day’s full event list; day turns “+N more” into a link that loads the Day view for that date. Popover ships with focus management (Esc, click-outside, focus restoration), aria-haspopup/aria-expanded, and role="dialog". Day-link mode ships zero JS.
• New month_overflow_action shortcode attribute / monthOverflowAction block attribute (values: popover | day).

0.7.4

• Fix: Multi-day events in the Cards view now render with a date range in the date column (“4–8 / MAI / man–fre” for same-month, stacked “30 APR ↓ 5 MAI” for cross-month) instead of showing only the start day. Previously a 5-day event like “Class trip Monday–Friday” looked indistinguishable from a single-day event in cards.
• Fix: Cards view with card_grouping = day now expands multi-day events into every day they cover, matching Week and Mini view behaviour. Previously a Monday–Friday event only appeared under Monday’s section. Week and month grouping keep the simpler “appear once at the start group” behaviour — the new date-range badge signals the span without multiplying cards across groups.
• All-day handling honours Google Calendar’s exclusive-end-date convention (a “Mar 5–7” event arriving as end=Mar 8 is correctly bucketed and labelled as Mar 5–7 inclusive).

0.7.3

• Docs: Moved CHANGELOG.md from the plugin root to docs/CHANGELOG.md. Plugin Check’s unexpected_markdown_file rule (severity 9 WARNING) flags any non-readme .md file at the plugin root.
• Docs: Trimmed this Changelog section (per Plugin Check’s 5000-character cap). Full history is in docs/CHANGELOG.md.

0.7.1

• Admin: Edit Display form fields no longer overflow under the sticky Live preview pane on the right. <select> elements had no width rule and auto-sized to their longest option text, clipping trailing characters behind the preview. Selects, plus input[type="number" | "url" | "date"], now share the same width: 100%; max-width: 520px cap as text inputs.

0.7.0

• New: “Card grouping” display option — groups cards in the Cards view under day, ISO week, or calendar month section headings, with a per-section event count. Defaults to off; existing displays render byte-identically until you opt in. Configured per display under “Card view options” in the admin, or via the card_grouping shortcode attribute / cardGrouping block attribute.

0.6.10

• Fix: Per-display label overrides (“Today”, “Tomorrow”, “All day”, etc.) are now honored by the shortcode/block pipeline. Same root cause as 0.6.9 — Shortcode::defaults() was missing the labels key.
• New: Gutenberg block now exposes “Event color override” as an Inspector control. Block users in inline mode (no saved display selected) had no UI to set the override before.
• Fix: Admin Live Preview now correctly renders the Upcoming view when configured. Was silently falling back to List.