Fixed: Badge variant truncated text mid-word. The badge layout has overflow:hidden and white-space:nowrap, but the segments inside didn’t carry data-fit-priority hints — so when the embed sat in a narrow column (e.g. the admin’s live-preview sidebar) the fit observer didn’t know which parts to hide and the “Powered by WFY24” link was clipped mid-letter. Now the powered-by link, the description, the “Feels like” segment, and their dividers each have priorities; the observer hides them cleanly in priority order until everything fits.
Fixed: “Add to sidebar” quick action shown for block-based themes. On themes like Twenty Twenty-Three that register no classic sidebars, the action would always end in “Could not auto-add to sidebar — please add the widget manually from Appearance → Widgets”. The button is now hidden on block-theme installs and replaced with a short note pointing to the Site Editor and the shortcode option.
Requires PHP 8.1 (was 7.4). PHP 7.4 reached end-of-life in November 2022 and is no longer receiving security patches. 8.1 is the lowest version Plugin Check / WordPress.org still recommends.
2.0.1
Fixed: AQI variant chips unreadable in dark theme. The pollutant chips (PM2.5, PM10, O₃, NO₂) were using a translucent overlay that resolved to near-invisible against the dark theme’s navy backdrop, leaving the value text floating on what looked like the bare widget bg. The chip background, text, and border now use solid theme-aware colors (slate-700 on navy in dark, white on pale-blue in light), and the chip text reads from a dedicated set of CSS variables that stay legible regardless of the cascade.
Version bump also serves as a Cloudflare-cache buster — the ?ver=2.0.0 query had been cached on the CDN with the original 2.0.0 bundle, so even after the widget.js fix landed on the origin, sites embedding the script kept loading the stale copy. ?ver=2.0.1 is a fresh cache key.
2.0.0
NEW: Air Quality (AQI) widget variant. A new variant=”aqi” style renders European-AQI air quality for the configured city — the big AQI index number, category band (good through hazardous, color-coded per the EEA scale), and the four headline pollutants (PM2.5, PM10, O₃, NO₂). Data comes from the Copernicus Atmosphere Monitoring Service (CAMS) via wfy24.com. Pick it from the “Style variant” dropdown in settings, or set it inline with [wfy24_weather variant=”aqi”].
Premium admin redesign. The plugin’s two separate admin screens — the onboarding wizard and the settings page — have been merged into a single unified screen at Settings → WFY24 Weather Widget. New 2-column layout with a sticky live preview on the right plus inline quick actions (create Weather page, add to sidebar) so you never need to leave the page to set up an embed. The old wfy24-welcome URL still works — it now redirects to the unified screen.
Re-organized settings. Essentials (city, language, theme, units, style) are upfront; visitor location, SEO JSON-LD, and the API key sit in a collapsible Advanced panel.
Embed snippet card with one-click copy-to-clipboard.
Removed: multi-city (cities=”…”). The v1.7.x multi-city feature is removed in this major release — the implementation needed a dedicated admin picker UI to be discoverable, and the new unified layout focuses on the most common single-city flow. If you had multi-city enabled, your shortcodes without cities= now fall back to your Default City; explicit [wfy24_weather cities=”…”] shortcodes will only render the first city. The wfy24_default_cities option is preserved on update so no data is lost in case the feature returns later.
widget.js is unchanged, so every existing shortcode and Gutenberg block in published posts continues to render exactly as before.
1.6.0
NEW: Schema.org JSON-LD output. Each widget instance now emits a server-rendered WebPageElement block describing the city (as Place), language, units, and provider. Helps search engines and AI agents understand that the page contains a weather forecast for a specific location — useful for semantic search, AI overviews, and future rich-result eligibility. Toggle from the settings screen (on by default).
Canonical URLs + localized names. The JSON-LD resolves each shortcode’s city against the wfy24.com search API on the server side, so the emitted url is the real canonical (e.g. https://www.wfy24.com/el/weather/thessaloniki-gr57554537) and the Place.name uses the language-correct form pulled from the translations table (İstanbul for tr, Θεσσαλονίκη for el, etc.). Cached in a WP transient for 24h on hit, 5min on miss — first page load makes one upstream call, all subsequent renders are cache hits.
Filter hooks for third-party customization: wfy24_jsonld_enabled (per-widget on/off) and wfy24_jsonld_data (modify the payload before emission).
No change to the visual widget — widget.js is unchanged. Existing shortcodes and blocks render exactly as before with the new JSON-LD appended.
1.5.6
Language combobox: clicking the field now shows all 50 languages, not just the saved selection. Previously, focusing the field with “English” already saved would self-match the filter and the dropdown would only show the single English entry — useless for switching language. Now the picker detects when the input value equals an existing language’s native or English name (i.e. the saved selection) and shows the full list so you can browse.
Both city and language inputs now select-all on focus, so typing immediately replaces the saved value instead of appending to it.
Removed the 12-item / 20-item slicing on the language list — the dropdown is scrollable, all 50 are now reachable.
1.5.5
Fixed: city and language suggestion dropdowns never opened. The combobox stylesheet sets display: none as the default state for the suggestion list; the JavaScript was clearing the inline override (element.style.display = ”) which fell back to that CSS default — so the dropdown was always hidden, even though the REST proxy was returning matches and no console errors were thrown. Now sets display: block explicitly. Affects both the Default City picker and the Language combobox on the settings and onboarding screens.
1.5.4
City picker UX matches the public wfy24.com search. The Default City dropdown now renders each result as a two-line item — country flag, bold place name, and a grey secondary line with region + country (e.g. “Athens” / “Attica, Greece”) — instead of a single concatenated label. The picker also forwards the admin’s locale to the upstream search so localized place names are returned.
Keyboard navigation in the city picker. ↑ / ↓ to move through results, Enter to select, Escape to close — same shortcuts as the public site’s search dialog. Hovered and keyboard-active items share a single highlight state.
Internal: /wp-json/wfy24/v1/cities now returns structured fields (slug, name, country_code, country_name, flag, region) instead of a single pre-formatted label. Cache key includes the locale so per-language responses don’t collide.
1.5.3
Onboarding overhaul. Step 1 is now a complete configuration form — admin email (editable inline; no need to leave the wizard for Settings → General), default city (autocomplete search backed by wfy24.com places API), language (searchable combobox with all 50 supported languages shown in their native script and English name), theme, units, and a visitor-geolocation toggle — all set in one place before activation. Click Activate and the widget is live with your exact configuration.
Visitor geolocation is now off by default. Previously the widget would call navigator.geolocation whenever no default city was set, which triggered a browser permission prompt on every visitor and silently broke when declined. Auto-detect is now an explicit opt-in checkbox; the default is to honour the admin-set city, which matches what 95%+ of sites actually want (e.g. a tourism site for Crete shouldn’t show a Swedish visitor’s local weather).
City picker. Type a city name and pick from results (slug + flag + country) instead of needing to know the wfy24.com slug format. Powered by a server-side proxy (/wp-json/wfy24/v1/cities) so the admin’s IP is never exposed cross-origin.
Language combobox. All 50 supported languages now appear in a searchable dropdown with native + English names; type-ahead filters by either. The free-text 2-letter code input is gone.
Stronger Pro pitch. The free-version notice now lists the full Pro feature set inline (no attribution, higher rate limits, priority support, custom CSS via theme tokens, historical data + analytics) instead of just “removes the link.”
Sticky settings access. A “Open plugin settings” button is now pinned on the onboarding screen, and a “Skip onboarding” link routes admins straight to Settings if they prefer to configure manually.
CORP header on widget.js + /api/widget/. The hosted bundle now ships Cross-Origin-Resource-Policy: cross-origin, which makes the widget work in cross-origin-isolated environments (e.g. playground.wordpress.net) that ship Cross-Origin-Embedder-Policy: require-corp.
1.5.2
Activation transparency. The onboarding wizard now displays an explicit, dynamic disclosure listing exactly what is sent to wfy24.com on click — the site domain, the administrator email currently configured in Settings → General (rendered live so the admin sees their own email before consenting), the site name, the WordPress version, the plugin version, and the locale. No visitor data is collected. Admins who want to register with a different email are pointed to Settings → General and asked to change it before clicking Activate.
Documented multisite behaviour explicitly: per-subsite onboarding, no automatic phone-home on Network Activation, domain-bound API key per subsite. See the new “Multisite Support” section.
1.5.1
Plugin Check compliance — replaced two wp_redirect() calls in the Pro flow (Stripe Checkout and Billing Portal) with wp_safe_redirect() plus a scoped allowed_redirect_hosts filter that whitelists checkout.stripe.com, billing.stripe.com, and pay.stripe.com. The redirect helper validates the target host against this list before issuing the redirect, falling back to a safe admin URL on mismatch.
Tightened the readme upgrade notice for 1.5.0 to fit the 300-character limit.
Cleaned up readme: the “External service” section and FAQ no longer reference the daily telemetry ping (removed in 1.4.0) — the plugin makes no scheduled outbound calls.
1.5.0
WP.org compliance: replaced inline <script> tags with wp_enqueue_script. All three call sites — the [wfy24_weather] shortcode, the admin-settings live preview, and the onboarding wizard preview — now register the widget bundle through WordPress’s enqueue API and emit a <div data-wfy24-widget …> placeholder where the widget should render.
The hosted widget bundle (widget.js) gained a third mount mode: it scans the DOM for [data-wfy24-widget] elements and renders inside the placeholder you mark, so WordPress hosts can keep the script in the page footer (per directory guidelines) without breaking in-place rendering. The legacy inline-<script> pattern still works unchanged for non-WordPress integrations.
Added the WordPress 6.3 strategy => ‘async’ enqueue option.
1.4.0
Removed the opt-in telemetry ping in line with the WordPress.org Plugin Directory guidelines on phoning home. The plugin no longer schedules a daily WP-Cron event and no longer sends domain / WordPress version / plugin version to wfy24.com. The Telemetry checkbox has been removed from the Settings page. Existing scheduled events are cleared on upgrade and on deactivation.
The Settings page no longer shows monthly request counts on the connection card (these were populated by the removed telemetry response). The card still shows the API key prefix.
No change to the widget itself or to the Pro flow. All remaining external HTTP calls (one-shot site registration, Pro status, Stripe checkout/portal) are part of the service the plugin exposes and only run in response to an explicit user action.
1.2.0
Pro tier. Added a Pro section to the plugin Settings page. One-click upgrade opens a Stripe Checkout session (€9/month); on successful payment the plugin is notified via webhook and the widget suppresses the “Weather by WFY24” attribution link. Existing Pro users see their renewal date and a “Manage subscription” button that opens the Stripe Billing Portal (update card, cancel, download invoices). Secure checkout via Stripe, cancel anytime.
The shortcode now reads the Pro status from a plugin option (refreshed hourly via /api/widget/pro/status) and passes data-attribution=”0″ or “1” to widget.js accordingly.
Added “Upgrade to Pro” actions on the Settings page. No behavior change for free-tier users — the attribution remains required on free.
1.1.2
Attribution compliance: the free version now displays an explicit disclosure notice in the onboarding wizard before activation explaining that the “Weather by WFY24” link will appear under each widget. User consent is captured via the “Activate now (free)” button click. Added FAQ entries explaining the attribution, the Pro upgrade path, and external service behavior. The widget script now respects a data-attribution attribute (hardcoded to “1” in the free plugin; Pro version sends “0” to suppress the link).
1.1.1
Plugin Check compliance: added translators comments, ordered placeholders (%1$s/%2$s), escaped block wrapper attributes, prefixed globals with wfy24_, removed load_plugin_textdomain (auto-loaded since WP 4.6), added nonce / enqueue justifications where required by the widget’s embed pattern.
1.1.0
Zero-friction onboarding — welcome wizard auto-registers your site with wfy24.com on activation (no copy/paste)
One-click Weather page creation — publish a “Weather” page with the widget ready to go
One-click sidebar integration — inject a compact widget into your first sidebar widget area
Connection status — Settings page now shows key status and monthly request count
Opt-in telemetry — daily anonymous ping so your wfy24.com dashboard shows active installs
Improved readme disclosure for external services
1.0.0
Initial release
Shortcode [wfy24_weather] with city, theme, lang, units, variant attributes
Gutenberg block under Widgets category
Settings page for defaults (API key, city, theme, units, language, variant)
