✨ 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 Kanban for WP-Polls

SleekView Kanban reads your WP-Polls polls table, groups polls by status into Open, Closed, Locked, and Draft columns, and lets your editors drag polls between columns to manage the live poll lifecycle without juggling separate WordPress admin filter views.

♾️ Lifetime License available

SleekView Kanban board for WP-Polls

Why WP-Polls editors need a kanban view

WP-Polls stores each poll in wp_pollsq with a numeric pollq_active column for status, where positive values mean open, zero means closed, and negative values are used for locked or hidden polls depending on how a site has been configured. Answers live in wp_pollsa and votes in wp_pollsip. The default admin is a single table, which means open and closed polls all sit in the same list with no clear separation.

SleekView Kanban reads wp_pollsq, groups rows by the pollq_active value, and renders one card per poll. Card fronts show the poll question, the total votes from the answers table, the time since the poll opened, and the question's category if your site uses one, so an editor can decide whether to close, lock, or reopen without leaving the board.

Dragging a card to Closed sets pollq_active to zero through the WP-Polls update routine, dragging to Locked sets the matching negative value, and dragging back to Open restores the field. Vote counts and the poll widget on the frontend update through the standard hooks the WP-Polls admin uses for each change.

Workflow

Build a WP-Polls kanban board in four steps

1

Connect SleekView to WP-Polls

Install SleekView, point it at the WP-Polls polls table, and choose whether you want to cover all polls or only polls tagged with a particular category. SleekView reads wp_pollsq directly and joins to wp_pollsa for vote counts when you want them on the card front for editors.
2

Pick the pollq_active column

Pick pollq_active as the status field to group by. SleekView recognises the WP-Polls convention where positive values mean open, zero means closed, and negative values mean locked, and lets you remap labels so the board uses the language your editorial team uses in the editor's daily work.
3

Choose what shows on each card

Pick the fields to show on each card: poll question, total votes, time since the poll opened, and the category when set. Cards keep a fixed height so the Open column stays scannable in busy weeks where dozens of polls run side by side across different sections of the site at once.
4

Enable drag-and-drop poll management

Turn on drag-and-drop, set which roles can move cards, and confirm the action per column. Moving a card calls the WP-Polls update routine so the poll widget on the frontend reflects the new state immediately, and any caches that depend on the active poll IDs are refreshed by the plugin.

Sample board

Sample WP-Polls board across active and closed polls

A live WP-Polls board showing recent polls grouped by pollq_active so editors can open new polls, close old ones, and review locked archives without leaving the board.
Draft
6
Best feature for next release?
Category: Product, 4 answers
Which workshop topic next month?
Category: Events, 5 answers
Preferred newsletter cadence?
Category: Marketing, draft
Open
12
Which framework do you use?
Votes: 482, opened 2d ago
Favourite WordPress hosting?
Votes: 1,204, 8 answers
Best time for the live demo?
Votes: 96, opened 6h ago
Closed
184
Top membership tier in 2025?
Closed, total votes: 3,201
Conference city preference
Closed, total votes: 612
Year-end community awards
Closed by editor Pia
Locked
9
Internal poll, board archived
Locked by Admin Karl
Decision poll, leadership only
Locked, votes hidden
Legacy poll, kept for record
Locked since 2024-11

Comparison

Default WP-Polls admin vs SleekView Kanban

Default WP-Polls admin list

  • The WP-Polls admin shows polls as one long list with status indicators inline on each row.
  • There is no clear separation between draft polls, open polls, closed polls, and locked archives.
  • Closing or locking a poll uses an inline button, which makes batch lifecycle work slow.
  • Vote counts and category appear on the row but are easy to miss in a long flat poll list.
  • There is no shared dashboard view of active polls across categories with live counts.

SleekView Kanban

  • Group wp_pollsq rows by pollq_active across Draft, Open, Closed, and Locked.
  • Card fronts show poll question, vote total, time since opened, and category at a glance.
  • Dragging into Closed sets pollq_active to zero through the WP-Polls update routine.
  • Locked is its own column so archived polls do not get reopened by mistake during cleanup.
  • Category-scoped boards keep editorial polls and engagement polls on separate workflows.

Features

What SleekView Kanban gives you for WP-Polls

Live poll lifecycle at a glance

Draft, Open, Closed, and Locked sit in one board with live counts. Editors can see at the start of a campaign how many polls are live and at the end of a campaign how many need to be closed, which keeps the poll widget on the site reflecting the current editorial calendar.

Drag uses WP-Polls update routine

Moving a card calls the WP-Polls update routine so the active flag changes through the same code the admin uses. The frontend widget reflects the new state immediately, and any caches that depend on the active poll IDs are refreshed by the plugin without any extra glue.

Category and section boards

Boards can be scoped to a single poll category, a section of the site, or all polls together. This means a product team can run their own board for product polls and an events team can run their own board for event polls, without stepping on each other's editorial cycle.

Audience

Editorial teams that manage polls on a kanban board

News sites with weekly polls

News sites run a weekly poll alongside the lead story. The board makes the cadence visible: each week's poll moves from Draft to Open on Monday, sits in Open until Sunday, and is dragged to Closed at the start of the next week without leaving the editorial dashboard.

Course sites with module check-ins

Course sites run short polls at the end of each module. The board groups module polls into Open while a cohort is active and into Closed once the module ends, so course leads can see at a glance which modules still need a final reflection poll set up.

Community sites with feedback polls

Community sites run feedback polls in waves. The board groups feedback polls by category, so the community lead can see all open feedback polls in one column and decide which ones to close or extend based on the response rate showing on each card front.

The bigger picture

Why a WP-Polls kanban gives small editorial teams a calendar

Polls are easy to start and easy to forget. That is the small problem at the heart of every site that runs WP-Polls. A poll goes up with a question, it gets some early votes, and then a week later it is still sitting on the homepage with stale answers because no one remembered to close it.

A kanban board fixes that quietly, because the Open column becomes the editorial calendar and the Closed column becomes the recent history. Each card carries its open date, so an editor can spot a poll that has been live for too long and either extend it or close it on the spot. Drafts sit in their own column waiting to be promoted, which makes the editorial pipeline visible to the whole team.

Locked polls have a separate place to live, so archived polls do not get accidentally reopened during a cleanup pass. Over a quarter, this lightweight discipline changes how a site uses polls. They become a regular feature instead of a forgotten experiment, the engagement they bring stays steady, and the editorial team has a board they can point at when they explain the rhythm of the year to a new hire who joined last week.

Questions

Common questions about SleekView Kanban for WP-Polls

Yes. SleekView calls the WP-Polls update routine so the pollq_active value changes through the same code the WP-Polls admin uses. The frontend poll widget reflects the new state immediately, and any caches that depend on the active poll IDs are refreshed by the plugin.

 

Each board takes a category filter or covers all polls together. Most editorial teams run a category board per major section of the site and a sitewide board for the editor in chief who wants to see every active poll across the publication on a single dashboard.

 

Yes. Card meta can include the total vote count joined from wp_pollsa, and SleekView refreshes the count when the board reloads or when the editor toggles the live update option. This keeps the editorial dashboard honest without manual refresh during a busy hour.

 

No. Each column can be configured to allow or deny incoming drags from any other column, so Locked can be set to a one-way destination. This means archived polls cannot be reopened without an explicit unlock action from an editor with the matching role permissions.

 

Yes. Scheduled polls live in the Draft column until their scheduled open date arrives, at which point the WP-Polls open routine runs on the cron and the card moves to Open automatically. The editor does not need to drag the card on the day the poll is scheduled to open.

 

Yes. The board can be set to read-only for specific roles, so contributors and authors can see what is live without being able to close or lock polls. The drag is hidden for those roles, and the move endpoints reject any attempted action that comes from a non-editor user.

 

Yes. The poll category, when set on the poll, is read from the WP-Polls meta and rendered on the card alongside the question and vote count. This makes it easy to spot a poll that is sitting in the wrong column or under the wrong section across a busy editorial dashboard.

 

Yes. SleekView pages each column, uses indexed queries on pollq_active, and only loads card fields for the visible columns. Large archives stay responsive because heavy fields such as answer lists are only fetched for the cards currently on screen at the editor's view.

 

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