SleekView Kanban for Meta Box Relationships
SleekView Kanban reads pairings created by Meta Box Relationships, groups them by a lifecycle state meta key, and lets editors drag connections between Draft, Active, Deprecated, and Archived. Both linked posts stay visible on every card front.
♾️ Lifetime License available
Why relationship links need a lifecycle view
Meta Box Relationships connects two WordPress post types through a many-to-many relation stored in wp_mb_relationships, with each row carrying a from post ID, a to post ID, order_from, order_to, and the relationship type slug. Sites use it to pair projects with clients or contracts with vendors, then mark whether the link is still in force on a meta field.
The default Meta Box Relationships admin renders connections as a meta box on the parent post editor with a sortable picker. That works for adding or removing a single pairing, but it gives editors no view of the lifecycle across the site. Counting how many pairings are still Draft, how many are Active, and how many were Archived for compliance requires opening each parent post one by one.
SleekView Kanban points at the pairings between two post types, groups rows by a Meta Box Select that holds the link state, and renders Draft, Active, Deprecated, and Archived as lanes. Each card shows both sides of the pairing through the wp_mb_relationships join. Dragging writes the new state through update_field, the relationship row stays intact, and Meta Box hooks fire on every drop.
Workflow
Build a relationship lifecycle board
Pick the relationship pairing
Show both sides on the card
Group by the lifecycle field
Enable drag-and-drop edits
update_field on the Meta Box Select. The relationship row stays untouched and Meta Box save hooks fire on every drop like a normal post edit.
Sample board
Sample pairing lifecycle board
Comparison
Default relationship meta box vs SleekView
Default relationship picker
- Relationships render as a meta box on each parent post with no lifecycle view
- No visual count of how many pairings sit in each lifecycle state across the site
- Advancing a state means opening every parent post and editing the Select by hand
- Bulk advance across a list of pairings is not possible from the picker screen
- Editors cannot see both linked posts side by side while triaging lifecycle states
SleekView Kanban
-
Joins the
wp_mb_relationshipstable so both linked posts appear on cards - Groups pairings by any Meta Box Select holding link state with live lane counts
-
Drag a card to advance the state through
update_fieldon the chosen meta - Archived lane keeps compliance-locked pairings out of Active counts on the board
- Capability gates restrict the Archived lane to senior leads with audit permissions
Features
What SleekView Kanban gives you for Meta Box Relationships
Both sides on every card
Meta Box Relationships pairings carry meaning through both posts. SleekView shows the from post and the to post titles on every card front, pulled through the standard wp_mb_relationships join with no extra queries.
Drag writes via update_field
Each move calls update_field for the lifecycle Select. The row in wp_mb_relationships stays untouched with its original from, to, and order values, while Meta Box save hooks fire so audit logic runs.
Archived for compliance
Compliance teams need a way to preserve pairings without keeping them in the active workflow. The Archived lane holds locked pairings out of Draft and Active counts, with capability gates for senior leads.
Audience
Teams that run pairing lifecycle workflows
Agency project teams
Agencies pair projects with clients and track each pairing through Draft, Active, Deprecated, and Archived. Leadership sees a live portfolio view and compliance keeps Archived locked for the books.
Legal contract teams
Legal teams pair contracts with vendors and track lifecycle on the board. Deprecated holds contracts no longer active, and Archived preserves expired contracts for the seven-year window.
Retail product catalogs
Retail catalogs pair products with suppliers and triage lifecycle on the board. Active products show live stock, Deprecated holds retired SKUs, and Archived locks SKUs for audit trail.
The bigger picture
Why a kanban beats a relationships picker
Meta Box Relationships pairings carry meaning across two posts at once. A project on its own is just a post, but a project paired with a client is an account, and that pairing has its own lifecycle independent of either side. A contract paired with a vendor goes through Draft while terms are negotiated, Active while it runs, Deprecated when a new contract replaces it, and Archived when compliance locks it for the audit trail.
The default Meta Box Relationships picker lets editors create and remove pairings one at a time from a parent post editor, but it gives no view of the lifecycle across every pairing on the site. A kanban board fixes that shape. The pairing becomes a card, both linked posts appear on the card front through the wp_mb_relationships join, and lanes give an instant count of how many pairings sit in each lifecycle state.
Drag-and-drop turns a state advance into a single gesture that calls update_field and fires every Meta Box save hook.
Questions
Common questions about SleekView Kanban for Meta Box Relationships
SleekView reads directly from the existing wp_mb_relationships table through Meta Box helper functions. No data is duplicated and no shadow tables are added. Uninstalling SleekView leaves every from and to row exactly where Meta Box Relationships wrote it on save.
Yes. The view config joins wp_mb_relationships once per page load and prefetches both linked post titles and any chosen meta in a single batched query. The card renders both sides with no extra per-card queries, so lanes load fast even for large pairing sets.
Only the lifecycle Select field updates through update_field. The wp_mb_relationships row keeps its original from, to, order_from, and order_to values, so the pairing itself stays intact. Meta Box save hooks fire so audit logs capture every state transition.
Yes. SleekView supports per-user filters on either linked post, so each manager sees only cards where their user ID matches a Meta Box User field on the from or to side. The same board configuration powers every manager view without duplicating any pairing data.
Dragging only updates the chosen Meta Box lifecycle Select through update_field. The row in wp_mb_relationships stays as Meta Box wrote it, with the same from, to, order_from, and order_to values, so the pairing connection remains intact across every drag.
Yes. The Archived lane supports a capability gate so only senior leads with the audit-permissioned role can drop a card in or out of it. Junior editors see Archived as a read-only lane with the count visible, but they cannot accidentally drag a locked pairing back into Active.
Yes. Many-to-many pairings are fully supported. Each pairing renders as one card, with the from post and the to post both visible on the front. Filter the board to one from post and every pairing rooted at that post appears as a separate card in the lane that matches its lifecycle.
SleekView reads the relationships table directly and uses the standard Meta Box helper functions. The free Meta Box plugin plus the Relationships add-on is enough to make the board work, though the paid AIO bundle adds more field types that can land on the card front.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout