Changelogs

Follow the improvements and fixes in each product release.

Products

Recent Releases

Permalink

Alpha Chat 0.1.7

Full Changelog: https://github.com/wpgaurav/alpha-chat/compare/v0.1.6…v0.1.7

Permalink

GT Link Manager 1.7.1

What’s Changed

  • Fixed: The GT Link toolbar now works with the core Button block by updating the Button’s native URL and rel attributes.
  • Improved: Rich text and Button controls now share the same GT Link search popover, normalize rel attributes, and preserve noopener for buttons that open in a new tab.

= 1.7.0 = = 1.7.1 = Fixes the GT Link inserter for the core Button block while preserving the Button block’s native link settings.

Commits

  • Fix Core Button link inserter (f9bbe5a)

Full Changelog: https://github.com/wpgaurav/gt-link-manager/compare/v1.7.0…v1.7.1

Permalink

GT ACF Blocks Plugin 2.9.2

What’s Changed

Changed

  • The migrator now strips the retired FAQ-schema flag from existing content. 2.9.1 made acf_accord_enable_faq_schema inert; this removes it (and its _acf_accord_enable_faq_schema field reference) from acf/accordion blocks when the migrator runs, so old posts no longer carry a key nothing reads.
  • Removals are reported under their own Retired FAQ schema flag removed category in the scan breakdown and per-post badges, rather than being folded into “Accordion fields fixed”.

Notes

  • Expect a one-time jump in the migrator’s affected-post count. Posts whose only issue is the stale flag now show up as needing migration. Rendering is unchanged either way — this is a data cleanup, not a fix for a visible bug, so it is safe to defer.
  • Accordion blocks with nothing to clean are left byte-identical and are not rewritten, so no post gains a revision for no reason.

Commits

  • 2.9.2: strip retired FAQ schema flag from existing content (b2b86b5)

Stats

  • Commits: 1
  • Changes: 5 files changed, 130 insertions(+), 14 deletions(-)

Plugin Info

  • Blocks included: 29
  • Requires WordPress: 6.0+
  • Requires PHP: 7.4+
  • Requires: ACF Pro 6.0+ or Secure Custom Fields

Installation

  1. Download acf-blocks-plugin-*.zip from the assets below
  2. Go to Plugins → Add New → Upload Plugin in WordPress admin
  3. Upload the zip file and activate
Permalink

GT ACF Blocks Plugin 2.9.1

What’s Changed

Removed

  • FAQ schema dropped from the Accordion block. Google no longer supports FAQ rich results, so acf/accordion no longer emits FAQPage JSON-LD and the “Enable FAQ Schema” field is gone from the block settings.
  • Existing posts need no migration: blocks that still carry acf_accord_enable_faq_schema set to 1 render normally, and the stored value is ignored — no schema is printed.
  • The block migrator no longer writes acf_accord_enable_faq_schema into blocks it converts.

The Accordion block itself is unchanged — same markup, same styles, still searchable by “FAQ” in the inserter.

Commits

  • 2.9.1: drop FAQ schema from accordion block (20c57e7)
  • Fix PHP 7.4 CI dependency resolution (2483e1d)

Stats

  • Commits: 2
  • Changes: 13 files changed, 76 insertions(+), 91 deletions(-)

Plugin Info

  • Blocks included: 29
  • Requires WordPress: 6.0+
  • Requires PHP: 7.4+
  • Requires: ACF Pro 6.0+ or Secure Custom Fields

Installation

  1. Download acf-blocks-plugin-*.zip from the assets below
  2. Go to Plugins → Add New → Upload Plugin in WordPress admin
  3. Upload the zip file and activate
Permalink

Core Forms 4.7.1

Fixed

  • Standalone and fullscreen form pages no longer fall back to browser-default controls when the global or per-form built-in theme is disabled.
  • Standalone routes now always load the complete Core Forms design baseline and generated theme-token overrides because these pages do not render the active WordPress theme.

Changed

  • The default form theme now depends on the core form stylesheet so its layout primitives are always present.
  • Added regression coverage for standalone asset loading.
Permalink

Core Forms 4.7.0

Core Forms 4.7.0 is the admin, design, migration, and Core Commerce release.

Highlights

  • Unified Core Forms, Submissions, Core Commerce, and Settings under one compact, responsive navigation.
  • Added a dedicated Form Theme Customizer with presets, live desktop/mobile preview, accessibility checks, and generated cache-versioned CSS.
  • Added selective portable JSON backup and restore for forms, submissions, polls, settings, analytics, and complete Core Commerce data.
  • Rebuilt Core Commerce around next actions, product readiness, customers, licenses, orders, and storefront publishing.
  • Added case-insensitive customer records with order, license, activation, and site metadata.
  • Added copy-ready product blocks and shortcodes plus single-product-page publishing guidance.
  • Replaced the all-submissions card grid with a searchable sortable table and improved responsive controls throughout the plugin.
  • Fixed starter-template previews, preview/frontend theme drift, Warm preset styling, LTR select arrows, checkbox alignment, and help text sizing.

Compatibility

  • WordPress 6.4 or newer
  • Tested through WordPress 6.8
  • PHP 8.1 or newer

Integrity

  • SHA-256: 9c4974ebe162f16790e7fc7c8927458473ca894b7abc2a57b20f13b9be537c4b
  • ZIP size: 1,097,202 bytes

Full public changelog: https://core-forms.com/changelog/

Permalink

Core Forms 4.6.3

Core Forms 4.6.3 improves validation, licensing reliability, headless submissions, and the Core Forms admin experience.

  • Renames the Forms dashboard to Core Forms, adds the installed version badge, and renames Products & Licensing to Core Commerce.
  • Fixes schema and legacy-form validation, same-name choice groups, empty select placeholders, and invalid-submission rate-limit accounting.
  • Fixes headless REST error statuses, nonce-enforced submissions, array-field normalization, and canonical field descriptions.
  • Fixes Emailit v2 sends and contact subscriptions being marked failed after a valid HTTP 200 response.
  • Makes activation records self-healing, retries transient license requests, and preserves the local key when remote deactivation fails.
  • Removes the redundant one-page Core Commerce footer and misplaced card treatment.
Permalink

GT Link Manager 1.7.0

What’s Changed

  • New: Geolocation targeting. Any link can route visitors to a different destination based on their country, with rules evaluated in order and the first country match winning.
  • New: Country detection with zero dependencies. The country is read from request variables your CDN or web server already provides — Cloudflare (CF-IPCountry), CloudFront, Vercel, Google App Engine, nginx GeoIP2, Apache mod_geoip, mod_maxminddb, or a custom header you name. No GeoIP database file, no third-party API, no outbound request.
  • New: EU country group expands to all 27 member states in a single rule; extendable via gtlm_geo_country_groups.
  • New: Per-rule status codes, and a “show a 404” fallback for visitors matching no rule.
  • New: Geolocation settings section with a live “Detected Now” readout showing which country and source resolved for the current request — the fastest way to confirm your CDN is forwarding a country header.
  • New: “Check Detection” button. Lists every country header present on the request with its raw value, and runs a loopback self-test — it sends the site a request carrying a country header and reports what the plugin detected at the other end. That proves detection works even on a local or staging install with no CDN in front, where “no country on this request” is correct rather than a fault. Also validates a country code you type before you use it in a rule.
  • New: The detection readout distinguishes “nothing is proxying this site, so no country is expected” from “your CDN is in front but sent no country header” — only the second is a misconfiguration, and it now says how to fix it.
  • New: Rule builder in the link editor. Numbered rows show match precedence, rules can be reordered, one-click picks cover common markets (US + CA, EU, UK, India, AU + NZ), the long country list is filterable, selections show as removable chips, and the “Everyone else” fallback reads as the final row. It warns when a country is listed twice (only the highest rule can ever match) or when a rule has countries but no URL.
  • New: Rule preview. Pick a country and see exactly which rule wins and where it sends — evaluated in the browser against your unsaved edits, with no request made.
  • New: Privacy disclosure. The plugin registers a suggested privacy-policy section under Settings → Privacy → Policy Guide, and states inline that country detection reads only a CDN-provided header — never the visitor’s IP address, never an external service, and the country is never stored or logged.
  • Fixed: a partial REST update (PATCH) of one field silently reset every field that was not included, because each write argument declared a schema default that WP_REST_Request materialises into the request. Sending only geo_rules would reset redirect_type to 301 — which quietly breaks geo targeting — and blank tags, notes, and rel. Omitted fields now keep their stored values. Create defaults are unchanged.
  • New: Optional X-GTLM-Country debug response header showing the detected country, its source, and whether a rule matched.
  • New: Geo rules are exposed in the REST API on /links (create, read, update) with a self-describing schema, so links can be geo-targeted programmatically. Posting geo_rules without geo_mode opts the link in automatically.
  • New: Geo rules round-trip through CSV import and export; a malformed rules cell is dropped without failing the row.
  • New: Geo column in the links list table, and geolocation status in Diagnostics.
  • Performance: geolocation costs nothing on links that do not use it — the check is a single array read, and country detection is never invoked unless a matched link opts in. Detection and settings are resolved once per request.
  • Note: geo-targeted links should use 302, not 301. A 301 is cached by the browser permanently, which pins a visitor to whichever country they were in on their first click. The link editor warns when a geo link is set to 301.
  • Note: a country header can be forged on requests that reach your site without passing through your CDN, so the 404 fallback is not a security control. Behind Cloudflare, CF-IPCountry is rewritten at the edge and cannot be spoofed; the “Cloudflare only” detection method is the strictest setting.

= 1.6.1 = = 1.7.0 = Adds geolocation targeting: route each link by visitor country using the header your CDN already sends — no GeoIP database, no external API, no added latency. Two columns are added to the links table automatically on upgrade; existing links are untouched and keep redirecting exactly as before. Enable it under GT Links → Settings → Geolocation Targeting.

Commits

  • Deploy the bare version to WordPress.org, not the tag name (03e7b9f)
  • Add geolocation targeting, bump to 1.7.0 (d45326c)
  • Add Playground blueprint for wp.org Live Preview (6ea77f0)

Full Changelog: https://github.com/wpgaurav/gt-link-manager/compare/v1.6.1…v1.7.0

Permalink

Core Forms 4.6.2

A public Storefront API for headless storefronts, plus a block editor and builder preview that finally look like the real form.

Added

  • Added a public, read-only Storefront REST API for static sites and external product embeds, exposing active-only product and plan data with resolved icons, hosted checkout URLs, filters, pagination, CORS, caching, and ETags.
  • The form skeleton (forms.css) and default theme (form-theme.css) now load inside the Block Editor canvas, so the Core Form block preview matches the published page instead of rendering unstyled.

Changed

  • The License Issuing Server no longer takes over an existing /checkout/ page it does not own. When that slug is already taken it provisions /core-checkout/ instead, leaving WooCommerce and hand-built checkout pages untouched.
  • Replaced every DOING_AJAX constant check with wp_doing_ajax(), which is filterable and the supported API.
  • Removed the orphaned AllSubmissionsTable::forms_dropdown() and ::date_filters() methods.

Fixed

  • Fixed the form builder preview pane painting unstyled before restyling itself. Its stylesheets were enqueued from a wp_head callback at priority 10, after core prints styles at priority 8, so they only ever reached the footer’s late-style pass.
  • Fixed the form builder preview request not being recognised as containing a form, which let the unused-asset cleanup dequeue the preview’s own stylesheets.
  • Corrected several inaccurate PHPDoc return types reported to callers and tooling, and declared Form::$id as the read-only alias __get() already served.
  • The licensing maintenance cron callback no longer returns its summary array to do_action().

Note: 4.6.1 was prepared but never published, so its changes are folded into this release and no v4.6.1 tag exists.

Requires: WordPress 6.4+ · PHP 8.1+ · Tested up to WordPress 6.8

Permalink

GT Extensions for FluentCart 2.2.0

What’s new

  • Add External Product with per-product URL, button text, link target, nofollow, sponsored, and price-visibility controls.
  • Replace storefront purchase controls across product pages, cards, and standalone FluentCart purchase blocks.
  • Redirect legacy instant-checkout links and reject external products in local cart and checkout validation.
  • Remove the bundled FluentCart Core and Pro source; FluentCart is now an independently installed dependency.

Requirements

  • WordPress 6.0 or newer
  • PHP 7.4 or newer
  • FluentCart 1.5.5 or newer for External Product and Multi-Currency Checkout
Permalink

Functionalities 1.4.8

What’s Changed

  • Improved: SVG Icon block now uses block metadata, lazy paginated icon loading, native block supports, px/em/rem sizing, original-color and monochrome modes, accessible labels, missing-icon recovery, and keyboard-friendly selection.
  • Security: SVG sanitization now requires a real SVG root, restricts styles and local references, blocks external href values, and prefixes definition IDs to prevent collisions.
  • Fixed: Fresh PWA settings now register rewrite endpoints immediately, and the offline application shell returns a cacheable success response so service-worker precaching can complete.
  • Added: True lazy module registry. A frontend request with all modules disabled loads no feature class files; enabling one module loads only that feature and shared dependencies.
  • Added: Versioned settings export/import with dry-run differences, module validation, default custom-code redaction, and an explicit code opt-in.
  • Added: Privacy-conscious diagnostics download with software versions, enabled modules, writable-path status, and rewrite-rule health. Task content, redirects, users, secrets, and site URLs are excluded.
  • Added: Redirect CSV import/export with common column aliases, all-or-nothing dry runs, and duplicate, wildcard, loop, and chain validation.
  • Added: Opt-in bounded 404 monitor with retention, row caps, path exclusions, bot/admin/API filtering, referrer-origin-only storage, purge, ignore, and redirect-prefill actions.
  • Added: Assumption Detection Site Health status, configurable scheduled scans, stale/failed scan distinction, and opt-in deduplicated email summaries.
  • Added: Content Integrity snapshot differences for links, headings, H1s, and word count, plus bounded audit metadata for baseline actions.
  • Added: Pull-request CI across PHP 7.4 through 8.5, WordPress Coding Standards, PHPUnit coverage, JavaScript/shell checks, version consistency, and distribution assertions.
  • Changed: Admin bootstrap is now a small router with dedicated module, portability, and Site Health controllers.
  • Fixed: Task Manager and Redirect Manager JSON updates now use locking, verified same-directory temporary files, and atomic replacement to prevent lost concurrent writes.
  • Fixed: Invalid JSON and storage failures preserve the last known file and surface an actionable admin error instead of silently appearing empty.
  • Fixed: SVG Icons is disabled on fresh installs, matching the explicit-activation policy used by every module.

= 1.4.7 = = 1.4.8 = Adds the upgraded SVG Icon block, safe settings portability, CSV redirects, an opt-in 404 monitor, native Site Health signals, true lazy module loading, atomic file storage, and pull-request quality gates. Existing option names, block names, shortcode syntax, admin URLs, hooks, and JSON formats remain compatible.

Commits

  • Improve SVG Icon block for 1.4.8 (9b797b8)
  • Fix PWA offline precaching on fresh installs (#49) (7ec31cc)
  • Ship Dynamic Functionalities 1.4.8 (#48) (85cc110)

Full Changelog: https://github.com/wpgaurav/functionalities/compare/v1.4.7…v1.4.8

Permalink

Core Forms 4.6.0

Core Forms 4.6.0 connects forms, payments, digital products, and software licensing in one native WordPress workflow.

  • Rebuilt Products & Licensing around searchable product, license, and order tables, product workspaces, setup checks, operational alerts, activity timelines, and validated plugin or theme release ZIPs.
  • Added product icons, sample-product generation, and optional purchase and renewal form generation for every active plan.
  • Added currency-to-gateway routing with multiple compatible gateways and a preferred gateway for each currency, plus native product checkout without a stored Core Form.
  • Expanded purchase templates for Stripe, PayPal, Razorpay, and Polar with optional business, tax, billing, phone, website, and order-note fields.
  • Added permissioned commerce REST endpoints and WordPress 6.9+ MCP-discoverable abilities for products, plans, releases, orders, licenses, subscriptions, downloads, gateways, and sample data.
  • Added blocks and shortcodes for product catalogs, product lists, single products, prices, buy buttons, checkout, and the customer dashboard, grouped in the Core Forms block category.
  • Removed customer emails and full license keys from newly generated renewal and package URLs, added enumeration-safe dashboard access requests, and recorded non-secret commerce activity events.
  • Corrected the plugin and installation-documentation product URL to core-forms.com.

Requires WordPress 6.4+ and PHP 8.1+.