Skip to content

v2.5.6 — Audit errors surfaced in the browser console

Choose a tag to compare

@JoshMilli JoshMilli released this 21 Jul 12:56
· 4 commits to main since this release

What's new

Diagnostics: audit failures are now readable from the dashboard — no server log access required.

2.5.5 made the audit endpoint catch fatal PHP errors and return the real message + file:line, but the dashboard still only displayed a generic "AI analysis unavailable / check debug.log" message, so the actual cause stayed hidden from anyone without WordPress log access.

2.5.6 fixes the frontend so the real error is visible:

  • The raw audit response (HTTP status + body) is always logged to the browser console.
  • A failed page logs its exact error and error_where (file:line) via console.error.
  • The on-screen notice now shows the real error text instead of pointing at debug.log.
  • The axios catch path dumps err.response.status + err.response.data, so even a hard HTTP 500 (a fatal above the per-page loop) is captured in the console.
  • The per-audit Retry button gets the same treatment.

This is a diagnostics release: it makes a failing audit debuggable directly from the dashboard so the root cause can be identified and fixed.

Update

Self-hosted update channel — sites will be offered v2.5.6 through the standard WordPress updates screen. Manual install: download conversion-iq-2.5.6.zip below and upload via Plugins → Add New → Upload.