SDAweb Calendar Sync for Google Calendar

Белешка о изменама

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

0.13.0

• Admin form reorganised — the Display edit screen now follows a clearer 7-section flow (Identity / View & layout / Date window / Appearance / Visitor experience / Outbound links / Localisation). All option keys preserved; existing displays load unchanged.
• Upcoming, Mini-month, and Label-overrides promoted out of the catch-all „Advanced“ disclosure into top-level sections matching the List/Card/Month pattern.
• New „Outbound links“ section consolidates four previously scattered link surfaces (event-link target, footer „See all“ link, Upcoming title-row „See all“, Mini-month full-calendar link) into one fieldset with subheadings.
• „Visitor controls“ renamed to „Visitor experience“; view-toggle + instant-swap controls grouped with the other visitor-side rendering options (search, hover popover, mobile fallback). Front-end render is byte-identical — admin-only change.

0.12.9

• Polish: admin URL placeholder examples changed from Norwegian https://example.com/kalender/ to English https://example.com/calendar/. Plugin source language is English; example strings should match. Affects three input fields on the display edit form (Upcoming „See all“ URL, Footer link URL, Mini-month full-calendar URL) plus the equivalent control in the Gutenberg block inspector. No functional change.

0.12.8

• Fix: per-view CSS now pre-loaded on every page that hosts a swap-enabled display. Per-view stylesheets were previously conditionally enqueued only for the view being rendered on the initial request — which broke after a swap to a view whose CSS wasn’t already in the document head („display totally messed up“ after clicking a toggle that targeted an unrendered view). The combined size of all view stylesheets is small (~6 KB), so pre-loading is the cleanest fix; avoids a runtime stylesheet-injection path in the swap module and the brief flash-of-unstyled-content that would produce. Also bundles the 0.12.7 fix for an undefined $context reference in View_Nav::render() that emitted a PHP warning on every prev/next anchor render — invisible when display_errors is off, but if on it injected into the response body and corrupted the JSON the swap module received.

0.12.7

• Fix: 0.12.6’s page-URL plumbing in View_Nav::render() referenced an undefined $context variable (the function takes $display_slug directly, not a context object). PHP 8+ emitted a Warning per request; when display_errors is on in the host’s PHP config, that warning text gets injected into the response body — corrupting the JSON returned to the swap module („display totally messed up“ after a swap). View_Nav::render() now takes $page_url as an explicit parameter; the four callers (Day/Week/Month/Mini renderers) pass $context->page_url. No more undefined-variable reference.

0.12.6

• Fix: view-toggle and prev/next anchor hrefs inside the REST-rendered partial were being built against the REST endpoint URL (/wp-json/sdaweb-gcal/v1/render) instead of the page URL, because add_query_arg() with no explicit base falls back to $_SERVER['REQUEST_URI']. Invisible to JS users (the swap module parses params from the href query string and ignores the pathname), but would have broken any non-JS path through the swapped HTML and produced incorrect URLs in any context that read raw hrefs (e.g. RSS-style aggregators, accessibility tools that surface link targets). Client now sends page_url=window.location.href as a REST param; server validates same-origin and uses it as the base for all toggle/nav anchor URLs. Per-page-URL cache partitioning added to the render cache + ETag so cached responses don’t cross-contaminate across host pages.

0.12.5

• Fix: instant view-swap now works end-to-end. Three issues from the 0.12.4 verification: (1) parseLinkIntent was reading the saved-display slug from root.dataset.sdawebGcalId, which actually holds the synthesised DOM identifier (sdaweb-gcal-<hash>), not the saved-display slug — REST endpoint correctly rejected it as unknown → 400 → swap fell back to native nav. Now reads sdaweb_gcal_id from the link’s query string (the authoritative source) with the root dataset as a fallback. (2) Hover/focus prefetch’s .catch() was returning null, which leaked through to applySwap() and crashed on data.html. Now re-throws so swap()’s own catch handles the fallback cleanly. (3) applySwap and announceToScreenReader gained null guards as defense-in-depth so any future malformed payload bails gracefully instead of throwing. The pushState URL is now also correct (it uses params.slug, which is now the proper value).

0.12.4

• Fix: instant view-swap now actually works. Root cause was MIME-type — LiteSpeed (and many other hosts without .mjs in their MIME map) served the script module as application/octet-stream, and browsers silently refuse to execute modules whose Content-Type isn’t a JavaScript MIME type. No error logged (the refusal happens before any module code runs), so symptoms were „module file present, all bytes correct, zero console errors, no click interception.“ Renamed swap.mjs → swap.js. WordPress’s script-modules API adds type="module" regardless of file extension; the .js extension is universally JS-MIME-mapped on every host. Diagnosed via Claude-for-Chrome inspection of the live response headers on stavdal.me.
• Also in 0.12.4 (rolled forward from a 0.12.3 test build that never shipped to wp.org): view-toggle anchors now carry data-sdaweb-gcal-view-toggle="<view-slug>" in addition to the existing BEM class. Swap module’s click delegate matches by either — defense in depth against future class refactors or theme-side class manipulation. Diagnostic logs from 0.12.2 remain gated by ?sdaweb_gcal_swap_debug=1.

0.12.2

• Diagnostic: instant view-swap module now emits gated console logs at every decision point (boot, target query, listener attachment, click match, intercept). Enable by appending ?sdaweb_gcal_swap_debug=1 to the URL, or by setting window.SdawebGcalSwap.debug = true before the module loads. Silent by default — no production impact. Surfaces the cause of „module loads but clicks fall through to full-page navigation“ reports without requiring code changes for diagnosis.

0.12.1

• Closing v0.12.0 gaps against the brief: REST response now includes cache: { hit, age_seconds } field derived from Render_Cache hit/miss state; Link: <home_url>; rel="canonical" header so caching layers indexing the JSON point back to the human site; swap:render:abort diagnostics event via connection_aborted() on client disconnect.
• Help tab gains „Instant view switching“ section explaining the feature, how to enable per display, when to disable for caching-plugin compatibility, and how to debug via window.SdawebGcalSwap.debug + the Diagnostics activity log.
• Feature flag default refined to match the brief: on for new displays, off for existing (the v0.12.0 release set both to off uniformly). Existing displays preserve their pre-0.12.0 full-page navigation behaviour on upgrade; new displays created post-upgrade have instant view swap pre-enabled.
• New: wp sdaweb-gcal rest-render <slug> CLI command for dispatching the REST endpoint internally + dumping JSON response to stdout — drives the new REST snapshot tests.
• New: wp sdaweb-gcal architecture-check --fixture=<path> CLI command — assert REST inner-HTML normalises to shortcode-pipeline inner-HTML for the same display config. Catches future drift between the two render paths.
• New: 3 REST snapshot fixtures (rest-list-grouped-by-day, rest-month-grid, rest-cards-anchor) + shared events fixture. Test runner extended to handle both HTML and JSON snapshots and to run the architecture regression check as a final pass.
• New: tests/boot-regression.html — browser-runnable assertion that swap.mjs’s boot path attaches its click listener correctly regardless of when DOMContentLoaded fires. Catches the bug class where a deferred ES module misses the DOMContentLoaded event and silently leaves the click delegate unwired.

0.12.0

• New: Instant view switching. Clicking the view toggle (List/Month/Card/Week/Day/Mini/Upcoming) or prev/next navigation now replaces only the calendar fragment — no page reload — with a smooth crossfade on supporting browsers via the View Transitions API. Falls back gracefully to full-page navigation when JavaScript is unavailable or the feature flag is off.
• New: REST endpoint /wp-json/sdaweb-gcal/v1/render for fetching individual view fragments. Public read; returns JSON with inner HTML + ETag + Cache-Control headers. 304 Not Modified support saves bandwidth on repeat navigations.
• New: Per-display feature flag „Enable instant view swap“ in the View section. Defaults off for safety — admin opts in per display after confirming compatibility with the site’s caching plugins. Dimmed (per v0.11.0 #6 pattern) when „Show view toggle“ is off.
• New: Hover/focus prefetch. Hovering or tab-focusing a view toggle speculatively fetches the target view; the subsequent click commits against a warm cache. Respects Save-Data and runs in requestIdleCallback so it never competes with user-driven work. Per-root LRU(6).
• New: Accessibility for AJAX swaps — aria-busy during fetch, screen-reader announcement after swap via a per-root live region, focus moves to the new view’s primary heading, prefers-reduced-motion skips the transition animation.
• New: Diagnostics integration. Every swap fires swap:render:ok/304/fail events into the v0.11.0 #12 ring buffer. Set window.SdawebGcalSwap.debug = true from the browser console for client-side timing logs.
• Bumped: Minimum WordPress version is now 6.5 (was 6.0) — required for the WP-native script-modules API the swap module uses.

0.11.1

• Compliance: silence 12 Plugin Check (PCP) false-positive errors from 0.11.0 — 9 OutputNotEscaped at the new Link_Target helper call sites (the helper returns a hardcoded attribute string, never visitor input — phpcs can’t trace escaping across function boundaries), 1 OutputNotEscaped on the CLI render command’s raw stdout echo (intentional for snapshot capture), and 2 MissingTranslatorsComment on the relative-time formatter (translator comments now sit on the line immediately preceding each __() call as the sniff requires). No runtime behavior change.

0.11.0

• New (#8): Centralised link-target helper. Every outbound link across every view now routes through View_Footer_Link-sibling helper Link_Target::attrs(), so the display’s „Open links in“ setting governs all link surfaces consistently. Mini-month full-link and Upcoming top-row „See all“ now also honour the setting (previously hardcoded to same-window). Footer link remains decoupled per 0.10.1.
• New (#1): Per-display render cache + cascade invalidation. Rendered HTML is now cached (15-minute floor TTL). Calendar „Refresh now“ cascades into every display containing the calendar, busting their render caches; the success notice surfaces the dependent-display count. New per-display „Refresh render cache“ row action on the Displays tab. Display form save and delete also bust automatically.
• New (#6): Consistent inactive-field dimming. Five conditional field groups in the display edit form now visibly dim with an inline „inactive — needs X“ badge when their master switch is off: Footer link 4 fields (gated by Show „See all“ link), Upcoming title cluster (gated by Show title row), Upcoming „See all“ URL (doubly gated), Mini-month link label (gated by URL non-empty), View toggle 2 fields (gated by Show view toggle). Dimmed fields stay interactive and persist values to the DB.
• New (#12): Diagnostics sub-panel in the Tools tab. Read-only introspection: per-calendar fetch state, per-display render cache hit/miss counters, environment summary, last-50 events ring buffer. Three action buttons: re-fetch all calendars, bust all render caches, download diagnostics JSON. Replaces the save → reload → guess debugging loop.
• New (#19, partial): WP-CLI commands. New wp sdaweb-gcal render <slug> for rendering a saved display to stdout, and wp sdaweb-gcal cache:bust [<slug>] for cache utilities. --fixture=<path> and --events=<path> flags enable deterministic snapshot testing via the new sdaweb_gcal_pre_fetch_events filter. Test fixture + bash runner + README under tests/ (not shipped in the wp.org zip). Snapshot-test feature is intentionally focused — --now flag, more fixtures, and CI wiring deferred to v0.12.0.

0.10.1

• Change: Footer link („See all →“) always opens in the same window now, decoupled from the display’s „Open links in“ (link_target) setting. Footer links are sibling-site navigation; event-row links continue to honour link_target for external Google Calendar event detail pages.

0.10.0

• New: Footer link („See all →“) on the bottom of List, Upcoming, and Card views. Five new admin fields under a „Footer link“ subsection in the View tab: show toggle, URL, label override, style (Quiet / Underline), and alignment (Auto / Start / Center / End). Auto resolves per-view: End for Upcoming, Center for List, Start for Card. Color follows the display’s Link color override (single source of truth across chips, top-row „See all“, and the new footer link). Empty URL hard-suppresses render. Coexists with the existing Upcoming top-row „See all“ — both can be enabled.

0.9.5

• Fix: Upcoming view — Title size, Title weight, and Uppercase title text settings actually take effect now. Shortcode::defaults() was missing the three keys, so shortcode_atts() was silently stripping them out of the config before it reached the view layer. The 0.9.4 patch (passing the keys through Display_Renderer::build_view_context) and the 0.9.3 CSS scoping change were both correct, but a third upstream layer needed the same keys to be added too. With the input gate now opened, all three controls work end-to-end.

0.9.4

• Fix: Upcoming view — Title size, Title weight, and Uppercase title text settings now actually take effect. The display orchestrator (Display_Renderer::build_view_context()) was missing the three keys from the options array it builds for the view, so the renderer always read empty values and fell back to its built-in defaults (15px / 500 / no transform). The renderer itself was correct; the upstream Display_Renderer is now passing the keys through. Visible only on title_uppercase until now — title_size and title_weight defaults coincidentally matched the renderer fallbacks, hiding the bug. 0.9.3’s CSS scoping change remains in place as defense-in-depth against themes that override text-transform directly on <span> elements.

0.9.3

• Fix: „Uppercase title text“ setting now applies correctly on the Upcoming view when the active theme has its own text-transform rule on <span> elements. Scoped the rule to .sdaweb-gcal-upcoming__title-text directly instead of relying on inheritance from the parent.

0.9.2

• Compatibility: Tested with WordPress 7.0.
• Cleanup: Suppressed a Plugin Check warning on the WP_DEBUG-gated error_log() diagnostic added in 0.9.1 (recurrence canary for the 0.9.0 native-color-picker swap bug). No behaviour change.

0.9.1

• Fix: Per-calendar Text color save bug introduced in 0.9.0. On the Calendars edit form, saving a Text color caused that value to land in the calendar’s main Color field instead, wiping the original Color value and leaving Text color blank. Root suspected in the interaction between the new wpColorPicker Text color field and the existing native <input type="color"> Calendar Color field (likely via the OS-level recent-colors memory the native picker exposes). 0.9.1 replaces the native picker on the Calendars tab with the same wpColorPicker control the Text color field uses — both fields now share the plumbing that the Displays-tab color fields have used for years without incident. If you saved a calendar in 0.9.0 with a Text color and find the swatch flipped to the value you picked: re-edit the calendar, restore the original Color, set the Text color again, and save.

0.9.0

• New: Tinted option added to Chip text color (Solid & Pastel) on the display edit screen. Derives a deep tint of the feed color in OKLCh that passes WCAG ≥ 4.5:1 against the actual chip background (raw feed for Solid, the pastel-tinted mix for Pastel). For light feeds (yellows, limes, cyans, light pinks), tinted text would be visually indistinguishable from black; the resolver detects that perceptual collapse and falls back to the Auto dark color automatically so authors don’t end up with a fourth option that’s secretly the third one. Pastel chips have more contrast headroom than Solid, so Tinted works on more feeds in Pastel.
• New: Per-calendar Text color picker on the Calendars tab (Color row). When set, this color is used as the chip text color for every event from that calendar, on every display, regardless of the display’s Chip text color setting. Live contrast badge in the picker checks against the calendar’s own background (Solid worst case); Pastel renders the same text on a softer tint and has additional headroom. Leave blank to let each display’s Chip text color setting decide.
• Change: Solid chip text color field renamed to Chip text color (Solid & Pastel) — Pastel chip titles now consume the same resolved text color as Solid through the shared --sdaweb-gcal-event-text custom property, so a single field governs both styles. Existing displays render unchanged when chip_text_mode is auto; Pastel chips opt in to the resolved color when chip_text_mode is light, dark, or tinted, or when the per-calendar Text color override is set.
• Fix: chip_text_mode (added in 0.8.3 as Solid chip text color) was not being copied from the saved display record into the render context, so every display rendered as if the mode were auto regardless of what the admin had selected. Always light and Always dark have been silent no-ops since 0.8.3; they now work as advertised.
• Fix: Visited chip and ribbon links lost their resolved chip text color. The global .sdaweb-gcal a:visited rule (specificity 0,2,1) out-specified the resting chip-anchor rule (0,2,0), so once a visitor clicked a chip link and returned the chip title flipped to the link color, undoing the Auto-mode WCAG choice and the new per-calendar override. Chip and ribbon anchor rules now list :link / :visited explicitly to bump specificity past the global rule.
• Fallback aggregator: when Tinted is selected and one or more selected feeds collapse to the Auto target, the display editor shows a single quiet note („N of M selected feeds fall back…“) under the field after save — no per-feed wall of warnings.

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.