Blocked Users
Auctions → Blocked Users — ?page=wkafw-users
A bidding ban list. Users on this list cannot place bids, register for events, or pay with their wallet. Existing bids stay in the database but are flagged.
What gets blocked
A blocked user:
| Action | Effect |
|---|---|
| Place bid | Bid form rejects with "Account suspended" error |
| Watch / favourite | Allowed (so admins can track) |
| Register for event | Rejected at checkout |
| Receive auction emails | Suppressed (configurable) |
| Use wallet | Top-up + transfer disabled; existing balance held |
| Withdraw | Rejected; admin must approve manually |
The block does not affect:
- Past won auctions and orders (those still complete)
- WP login (use a separate plugin to ban login)
- Storefront browsing (read-only access remains)
Page layout
| Column | Source |
|---|---|
| User ID | WP user ID |
| Name | display_name |
| user_email | |
| Reason | admin-supplied note |
| Blocked by | admin who placed the block |
| Blocked at | timestamp |
| Expires | optional unblock date (null = permanent) |
| Actions | view profile / unblock |
Filter by reason, expiry status, or search.
Adding a user to the list
Three ways:
| Method | Where |
|---|---|
| Manual | This page → Add User → search → reason → Save |
| From Bids | Bids → row → Block bidder |
| From Disputes | Disputes → resolution → Block buyer |
| From Fraud | Fraud Detection → flagged user → Block |
When adding, you can set:
- Reason — required free-text
- Expiry — optional date; defaults to permanent
- Notify user — send a courtesy email explaining the block
Auto-blocking
Fraud Detection can auto-block users when rules trigger:
| Trigger | Default block |
|---|---|
wkafw_bid_rate_limit exceeded N times | 1-day temp block |
| Repeated chargebacks | Permanent |
| Failed KYC after 3 attempts | Pending-review block (manual unblock) |
| Multiple disputes per month | Manual review |
Configure thresholds in Fraud Detection.
Unblocking
| Action | Effect |
|---|---|
| Unblock (per-row) | Removes from list; user can bid again immediately |
| Bulk unblock | Select rows → Apply |
| Auto-expire | Rows with an expiry date auto-clear at midnight UTC |
Unblock writes a row to the Audit Log and emails the user.
Bulk actions
| Action | Effect |
|---|---|
| Unblock | Lift the block |
| Extend | Push expiry by N days |
| Make permanent | Remove expiry |
| Export CSV | Selected rows |
Per-page count
Configurable via wkafw_blocked_users_per_page option (default 20). Override in Auctions → Settings → General.
Privacy
Blocked-user records contain personal data — manage them per your privacy policy. The plugin's GDPR exporter (under WP Tools → Export Personal Data) includes block records keyed to the user's email.
Common workflows
"Block a confirmed bot"
- From Bids, filter by suspect IP or pattern
- Identify the user
- Block with reason "Bot activity — IP correlation"
- Add the IP to a Fraud Detection rule
"Temporary cool-down for a hot-headed bidder"
- Add User → search
- Reason: "Disruptive bid retraction pattern"
- Expires: 7 days from now
- Notify user: yes
"Annual block-list cleanup"
- Filter: expired temp blocks
- Bulk select → Unblock (auto-expiry usually handles this, but a manual sweep catches edge cases)