✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Social Login Pro: provider links and history as tables

Social Login Pro persists OAuth links in wp_usermeta and login attempts in a custom wp_sl_login_attempts table. SleekView joins both into one grid with user, provider, attempt status, and timestamp.

♾️ Lifetime License available

SleekView table view for Social Login Pro

Provider links and login attempts on one grid

Social Login Pro is a multi-provider OAuth plugin that links each user via wp_usermeta entries (one per provider) and writes an audit row to wp_sl_login_attempts on every login attempt, successful or not. The plugin's admin focuses on configuration and a summary chart, with no row-level table for the attempt history or the linked-provider matrix.

SleekView reads both sources and presents one row per attempt or one row per user, depending on the saved view. The attempts grid carries user, provider, attempt timestamp, success flag, and error string when present. The linked-provider grid pivots wp_usermeta on the plugin's provider keys, with one column per provider per user, joinable to the attempt history for incident response.

Edits route through the plugin's unlink and revoke handlers when available, and fall back to direct meta and table writes with a clear admin warning. The attempt log is read-only by default so the audit trail stays intact; archival or purge actions are exposed as explicit bulk operations rather than inline edits.

Workflow

From summary chart to a real attempt log

1

Pick the source

Point SleekView at wp_sl_login_attempts for the attempt grid and wp_usermeta with the sl__id prefix for the linked-provider pivot.
2

Compose two views

Attempt view: user, email, provider, timestamp, outcome, error. Linked-provider view: one column per provider, joined to last-login and link date.
3

Scope per role

Security ops gets full read on attempts and read-write on archive. Support gets read-only attempts plus user-search filters. Identity admins get the linked-provider pivot with unlink rights.
4

Triage and edit inline

Filter failed attempts by provider, retry through the plugin's hook, archive old rows in bulk. Linked-provider unlink also routes through the plugin's documented revoke action.

Sample columns

A typical login-attempts view

Joins wp_sl_login_attempts to wp_users so each row carries the user, the attempted provider, and the outcome.
Source: wp_usermeta (sl__id keys) + wp_sl_login_attempts
User Email Provider Attempted Outcome Error
alex_studio alex@studio.co Google Apr 24 09:12 Success
ria_design ria@design.io Facebook Apr 24 08:55 Retry Token refresh required
tom_hello tom@hello.dev Twitter Apr 23 18:20 Failed Scope changed
mia_brew mia@brew.coop LinkedIn Apr 23 15:04 Success

Comparison

Default Social Login Pro admin vs SleekView

Default Social Login Pro admin

  • Login-attempt history is summarised, not exposed as a sortable row table
  • No cross-provider filter on the user-by-provider link matrix
  • Per-attempt error string is buried; admins read summary counts instead
  • Bulk-unlink across users requires direct SQL on wp_usermeta
  • No archive or purge tool for old rows of wp_sl_login_attempts

SleekView

  • Row-level login-attempt log with provider, outcome, and error columns
  • Pivot wp_usermeta per provider for the linked-user matrix
  • Filter to retry-required attempts to catch token refresh issues fast
  • Bulk-unlink through the plugin's revoke hook with an audit trail
  • Archive old wp_sl_login_attempts rows as an explicit bulk action

Features

What SleekView gives you for Social Login Pro

Row-level attempt history

Every entry in wp_sl_login_attempts appears as a row, with provider, outcome, and error fields surfaced inline. Triage failed logins in one filter instead of summary charts.

Linked-provider pivot

Each provider column lights up when a user has the matching sl__id meta row. Filter to single-provider users when planning a connector sunset.

Audit-safe archive

Archive attempt rows in bulk with a retained audit log. The plugin's GDPR data export still references the originals; SleekView writes archive timestamps without deleting evidence by default.

Audience

Who uses SleekView for Social Login Pro

Security ops

Filter failed attempts by provider and outcome to spot scope changes and brute-force patterns. The error column on wp_sl_login_attempts is the field the SOC actually wants.

Support agents

Pull a user's last ten attempts in one click, see exactly which provider failed and why, and confirm the right fix before responding. Three steps, one grid.

Identity admins

Plan deprecations by filtering the linked-provider matrix to users connected only to the provider being sunset. The pivot is the migration map.

The bigger picture

Social-login audit logs are the most under-used security data on most sites

Every site running Social Login Pro accumulates a long, detailed log of login attempts that the default admin only summarises. The summary is useful for dashboards and useless for incident response. When Twitter changes a scope or Facebook deprecates a permission, the affected users surface as a wave of failed-attempt rows in wp_sl_login_attempts long before anyone reads the chart, and the error column carries the exact message that explains the failure.

Security ops, support, and identity admins all need that row-level data and all three are currently underserved. SleekView turns the attempt log into a first-class operational grid with provider, timestamp, outcome, and error columns, joinable to the user and to the linked-provider matrix. Failed-attempt clusters become obvious in seconds.

Token refresh queues become a single bulk action. Linked-provider deprecation planning runs off the same join. None of this requires new data; it requires the right view of the data the plugin already writes.

Questions

Common questions about SleekView for Social Login Pro

Not by default. wp_sl_login_attempts is treated as an append-only audit log. Archive and purge actions are exposed as explicit bulk operations with a confirmation step, never as silent background edits.

 

Yes within reason. The view is configured against a meta-key prefix; if your install runs Social Login Pro alongside another connector that uses a different prefix, you save two views or compose a unified view that joins on the user id and merges columns.

 

Export and erasure routes still go through WordPress core's privacy tools and the plugin's own GDPR integration. SleekView is a read-and-write surface for the same data; it does not introduce a parallel privacy path.

 

Access and refresh tokens live in usermeta and are treated as sensitive by SleekView. They are never displayed in the grid or exported to CSV by default. The grid surfaces the link identifier and the audit columns, not the token itself.

 

Yes. Unlink and revoke actions route through the plugin's documented hooks so any downstream behaviour (audit logging, analytics counters, related-table updates) fires the same way it would from the plugin's own admin.

 

The grid uses indexed columns on attempt timestamp and user id, paginates server-side, and supports archive thresholds so a multi-year log stays responsive. The plugin's own summary charts continue to read the same rows.

 

If the plugin writes IP or session to wp_sl_login_attempts, the column appears as an optional filter. SleekView only exposes what the plugin stores; it does not capture additional request data.

 

Yes. The attempt table and meta rows are per-site by default and SleekView reads the current site context. Network-wide audits can be composed as separate saved views per site or a union across prefixed tables.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView