Skip to content

Releases: adamastbury/wondershield

v1.6.1

Choose a tag to compare

@github-actions github-actions released this 27 Aug 10:42

Full Changelog: v1.6.0...v1.6.1

v1.6.0

Choose a tag to compare

@github-actions github-actions released this 15 Jul 13:28

Full Changelog: v1.5.40...v1.6.0

v1.5.40

Choose a tag to compare

@github-actions github-actions released this 15 May 09:56

Full Changelog: v1.5.39...v1.5.40

v1.5.39 — Sync attempt events to Central

Choose a tag to compare

@adamastbury adamastbury released this 25 Mar 13:27

What's changed

  • Sync 'attempt' events: wp-login.php and wp-admin visits by unauthenticated users are logged locally as attempt but were excluded from the queue sent to Central. This meant the main signal for brute-force and credential-stuffing activity was invisible in the dashboard. attempt is now included in the event types synced to Central.

Full Changelog: v1.5.38...v1.5.39

v1.5.38 — Fix GitHub update cache

Choose a tag to compare

@adamastbury adamastbury released this 25 Mar 12:50

What's changed

  • Fix auto-update cache TTL: CACHE_TTL was set to 30 seconds, causing the plugin to hit the GitHub API up to 120×/hour per site. GitHub's unauthenticated rate limit is 60 req/hr per IP, so this was regularly triggering 403 errors and silently breaking auto-updates on busy or shared-hosting installs. Changed to 3600 seconds (1 hour).

Full Changelog: v1.5.37...v1.5.38

v1.5.37 — Retry event push on failure, restore queue

Choose a tag to compare

@adamastbury adamastbury released this 25 Mar 12:27

What's changed

  • Event push reliability: Switched from fire-and-forget (blocking: false) to blocking with 5s timeout. If Central returns a 4xx/5xx or the request errors, the event queue is restored so events are retried on the next flush rather than silently lost.
  • Rate-limit reset on failure: Resets ws_central_last_event_push to 0 on failure so the retry happens on the next request rather than waiting 60s.

Why

Events for some sites were silently dropping whenever Central returned an error. The plugin was clearing the queue before sending, so any transient failure permanently lost those events.

Full Changelog: v1.5.36...v1.5.37

v1.5.36

Choose a tag to compare

@adamastbury adamastbury released this 25 Mar 10:08

Adds /wp-json/wondershield/v1/health endpoint for WonderShield Central uptime monitoring.

Full Changelog: v1.5.35...v1.5.36

v1.5.35 — Permanent block page

Choose a tag to compare

@adamastbury adamastbury released this 24 Mar 21:09

What's new

  • Permanent block page: IPs blocked manually via WonderShield Central now see a distinct block page — "You have been blocked" heading, a "Manual review required" notice, and no countdown timer. Temporary auto-blocks are unchanged.

Full Changelog: v1.5.34...v1.5.35

v1.5.34

Choose a tag to compare

@adamastbury adamastbury released this 24 Mar 13:20

Fix: blocks not syncing to Central due to UTC/BST timezone mismatch in SQL query

Full Changelog: v1.5.33...v1.5.34

v1.5.33

Choose a tag to compare

@adamastbury adamastbury released this 24 Mar 13:07
  • Active IP blocks now sync to Central every ~60 seconds (via event flush)
  • New remote block endpoint — allows permanently blocking IPs from the Central dashboard

Full Changelog: v1.5.32...v1.5.33