Skip to content

v2.0.86: Fix Settings badge blind to broker, fix Test Connection requiring keys

Choose a tag to compare

View all tags
@mbheramil mbheramil released this 28 Aug 18:47
· 16 commits to main since this release
v2.0.86
5728cae

The bug

Sites relying on the automatic broker connection (added in v2.0.85) with no AWS key of their own were showing "Not configured" on the Settings page, even though AI was actually working correctly. The status badge was computed independently of the broker logic — it only ever checked for a raw access/secret key pair, a check that predates broker support.

Clicking "Test Connection" made it worse: it hard-required typing in an Access Key and Secret Key whenever wp-config.php constants weren't set, so even a site that's genuinely fine via the broker couldn't test its real connection at all.

The fix

  • The status badge, the Test Connection button, and its underlying handler all now reflect the real, broker-aware configuration state.
  • A clear note appears when a site is running purely on the automatic connection: "This site is connected automatically — no AWS credentials are needed here."
  • Test Connection now tests the real, current connection (broker or direct AWS) when both key fields are left blank — only requires typing in keys if you're testing new credentials.

Verified with an 8-assertion harness covering every real state: no keys with no prior attempt, no keys with a confirmed-working broker connection, no keys with a confirmed-not-authorized site, and a site with its own direct AWS keys.

Assets 2
Loading