# Changelog All notable changes to BW Dev are documented here. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). ## [Unreleased] ## [1.13.2] - 2026-05-29 ### Changed - **Animate Row: feature disabled site-wide pending a proper rewrite.** The 1.13.1 patch (skip above-the-fold + `AOS.refreshHard()` on `window.load`) fixed the blank-hero symptom on promptvictoria.ca, but a follow-up report showed that below-the-fold rows then never revealed either. Rather than ship another partial fix, the entire Animate Row pipeline is short-circuited: `enqueue_assets()` returns immediately, so no AOS CSS or JS is enqueued on any frontend page on any site. Per-site enable state and saved configuration are **preserved untouched** in `bw_dev_settings[animate_row]` for when the feature is rewritten and re-enabled. The settings tab now shows a prominent warning notice at the top explaining the disablement and recommending Kadence's per-block "Advanced → Block Animation" controls as an interim path. The Modules-tab toggle still exists but has no effect while this short-circuit is in place. To re-enable later: delete the early `return` at the top of `enqueue_assets()` in `class-bw-dev-module-animate-row.php`. ## [1.13.1] - 2026-05-29 ### Fixed - **Animate Row: blank above-the-fold content on live sites.** Reported on promptvictoria.ca (Flywheel). The module was blanket-stamping `data-aos="fade-up"` on every Kadence row/section, including the hero. AOS's `[data-aos^=fade] { opacity: 0 }` rule kicked in immediately, but AOS's reveal logic reliably failed to add `aos-animate` to elements that were already in the initial viewport (a known weakness with tall heroes, bg-video parents, and transformed ancestors) — leaving the hero stuck at opacity 0 forever, rendering a blank page. **Two fixes:** (1) `applyAnimations()` now skips any element that intersects the initial viewport (`getBoundingClientRect().top < viewportH && bottom > 0`), so above-the-fold rows are never opacity-hidden in the first place — they just appear normally, which is what you want for hero content anyway. (2) Added a `window.load` listener that calls `AOS.refreshHard()` so the offsets-cache is rebuilt after images / iframes / bg videos finish loading and shift the layout (this catches the secondary class of stuck elements just below the fold). ### Changed - **Analytics: removed the "Emit GTM tags" toggle.** GTM emission is now keyed solely off the `gtm_id` field — non-empty → emit, empty → skip. Eliminates the separate checkbox and the `GTM-NOIDSET` placeholder behavior (placeholder injection no longer happens; an empty field means no GTM markup at all, which is what users expected). One less click to configure. The settings tab also drops the "Markup that will be emitted" preview block — it was wall-of-code clutter and the real source of truth is viewing the live site. Migration is implicit: any saved `gtm_enabled` key is ignored. Sites with a non-empty `gtm_id` keep emitting; sites with an empty ID stop (matching the new and clearer behavior). To pause GTM on a live site after this update, clear the GTM ID field (or disable the whole Analytics module on the Modules tab). ## [1.13.0] - 2026-05-29 ### Added - **Analytics module** (`analytics`, group `frontend`) — drops Google Tag Manager script tags + the Search Console verification meta into every frontend page (admin / login / REST stay untouched). Two independent features: - **GTM**: gated by an in-module "Emit GTM tags" checkbox that defaults OFF (so updating bw-dev on an existing client site doesn't surprise-inject tracking). When on, the `` snippet hooks `wp_head` priority 1 and the `