Releases: eightam/eightam-gravity-cap
Releases · eightam/eightam-gravity-cap
Release list
1.2.6
- Re-released the
get_field_label()fix. The v1.2.5 tag was cut from the commit before that fix, so the published 1.2.5 package still carried the fatal error. - The updater no longer hardcodes the plugin's directory name. Installs unpacked into a versioned folder (e.g.
eightam-gravity-cap-1.2.5) were never matched against the update transient and so were never offered an update at all. - Updates now unpack into the directory the plugin already occupies. Releases without an attached zip fall back to GitHub's zipball, which unpacks as
eightam-eightam-gravity-cap-<sha>/and would otherwise install a second copy alongside the active one.
1.2.5
v1.2.4
v1.2.3 — Frontend fixes and CDN fallback
What's new
1.2.3
- Fix: duplicate widget rendering on some forms. The inner container shared an
idwith the outer Gravity Forms wrapper, which caused the<cap-widget>web component'sconnectedCallbackto fire twice (visible as two trigger checkboxes inside one shadow root). Inner container now usesinput_X_Yto match the label'sforattribute. - Change: the field's visible
<label>is no longer rendered on the frontend. Screen readers still get an accessible name viaaria-labelon the widget container. Label and label-placement settings are also hidden in the editor.
1.2.2
- Probe the Cap server's
/assets/widget.jsendpoint on settings save; fall back to a public CDN (jsDelivr, pinned to@cap.js/widget@0.1.51) whenENABLE_ASSETS_SERVERis off or the endpoint is unreachable. Re-checked every 6h. - Fail-open on
siteverifynetwork errors and 5xx responses (logged as errors), so a broken Cap server doesn't lock users out of forms. - Removed dead
type="module"script-tag filter (widget is an IIFE).
1.2.1
- Load the Cap widget directly from
{cap_server_url}/assets/widget.jsinstead of bundling it. RequiresENABLE_ASSETS_SERVER=trueon the Cap server.
v1.2.0
Full Changelog: https://github.com/eightam/eightam-gravity-cap/commits/v1.2.0