SleekView for Lingotek Translation: documents and statuses as tables
Lingotek Translation extends Polylang with hosted translation workflows, storing document state in wp_options and wp_postmeta alongside Polylang's translation taxonomy. SleekView surfaces every document and its workflow phase as one filterable table.
♾️ Lifetime License available
Lingotek workflows without the dashboard hop
Lingotek Translation runs on top of Polylang, which means it inherits Polylang's taxonomy-based language storage in term_taxonomy and term_relationships, then layers its own document and workflow state into wp_postmeta entries like _lingotek_document_id, _lingotek_phase, and _lingotek_last_modified. The default Lingotek admin lists documents one screen at a time, with filters that reset between sessions.
SleekView reads the Lingotek postmeta alongside Polylang's term taxonomy and exposes each document with current phase, target languages, last-modified, and assigned translator as columns. Filters like phase = in-review, or stale-since-March, or target = de_DE, become saved views that match the way a real localization team thinks.
Edits to phase or notes write back through Lingotek's own API where available, so the workflow stays consistent with what the hosted Lingotek dashboard sees. The grid is an audit layer, not a parallel system of record.
Workflow
From Lingotek dashboard hops to one document grid
Read Lingotek postmeta
_lingotek_document_id, _lingotek_phase, and related keys, joined with Polylang's taxonomy for language data.
Pivot by target language
Save workflow views
Update phases inline
Sample columns
A typical Lingotek document view
wp_postmeta (_lingotek_* keys) + Polylang term taxonomy on standard WP tables
| Document | Source | Phase | Target | Translator | Last updated |
|---|---|---|---|---|---|
| Homepage hero | EN | Published | DE, FR, ES | alex@studio.co | Apr 24 |
| Pricing page | EN | In review | DE, FR | ria@design.io | Apr 18 |
| Spring campaign | EN | In translation | FR, IT | tom@hello.dev | Apr 12 |
| Legacy blog post | EN | Failed | DE | mia@brew.coop | Mar 04 |
Comparison
Default Lingotek Translation admin vs SleekView
Default Lingotek Translation admin
- Document list paginates without cross-language pivot
- No saved views for specific workflow phases
- Filters reset between sessions
- Failed documents are hard to spot among in-progress ones
- Bulk reassignment of translators across documents takes many clicks
SleekView
- Every document with phase, target languages, and translator in one table
- Saved views for phase = failed or stale-since-March
-
Filter by translator assigned in
_lingotek_translator - Inline phase edits route through the Lingotek API
- CSV export for status reports and translator briefs
Features
What SleekView gives you for Lingotek Translation
Documents as rows
Each Lingotek document surfaces as a row with source language, target languages, current phase, and translator pulled from _lingotek_* postmeta.
Find failed and stalled
Save a view for phase = failed or stalled-over-fourteen-days to keep the workflow honest without opening the hosted dashboard.
Inline phase updates
Move a document between phases directly from the grid. Writes route through Lingotek's API so the hosted dashboard sees the same state.
Audience
Who uses SleekView for Lingotek Translation
Localization managers
Track every document by phase and target language without flipping between the WordPress and Lingotek dashboards.
Translation vendors
Pull a CSV of documents assigned to a specific translator with phase, source URL, and target language as columns.
Site owners
Report translation throughput by month, phase, and language for stakeholder reviews without manual screenshots.
The bigger picture
Why Lingotek workflows need a queryable WP-side surface
Lingotek's strength is its hosted translation workflow with phases, translators, and review steps. Its weakness, from the WordPress operator's chair, is that those phases live partly in the hosted dashboard and partly in wp_postmeta keys that the default plugin admin paginates without a meaningful filter. A localization manager running a content sprint across five target languages needs to see every document and every phase in one place, not two browser tabs.
Reading the _lingotek_* postmeta directly, joined with Polylang's language taxonomy, gives that surface inside WP admin. Saved views like in-review-for-French or stalled-over-fourteen-days load with one click, translators get scoped CSVs of their assigned documents, and site owners can report monthly throughput without manual screenshots of the hosted dashboard. Inline phase edits route through the Lingotek API, so the hosted system stays the source of truth and the grid never becomes a parallel database.
The result is faster sprints, clearer handoffs, and an audit trail that any new team member can read in five minutes.
Questions
Common questions about SleekView for Lingotek Translation
Lingotek extends Polylang, so language and translation relationships live in standard WordPress term taxonomy. Workflow state is stored in wp_postmeta under keys like _lingotek_document_id, _lingotek_phase, and _lingotek_last_modified.
Yes. Lingotek Translation runs on Polylang's language model, and SleekView reads both schemas together to show coverage and phase in one row.
 Yes. Phase updates route through the Lingotek API, so the hosted Lingotek dashboard sees the same workflow state as the WordPress side.
 
Yes. Save a view for stalled-over-fourteen-days using _lingotek_last_modified and the current phase. The view reloads with one click each sprint.
Yes. Lingotek and Polylang both handle term translations through the same taxonomy structure. SleekView includes a terms view alongside the documents view.
 No. SleekView queries Lingotek postmeta only when an admin loads a view and paginates server-side. Front-end Polylang language switching and Lingotek API calls are untouched.
 
Yes. Filter by _lingotek_translator, then export the visible columns to CSV. Translators receive a scoped brief rather than a full document list.
Yes. A view for phase = failed surfaces stuck documents with their last modified date and Lingotek document id, ready to retry through the Lingotek API.
 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 checkoutBrowse more
- Automatewoo
- Woocommerce Stamps
- Woocommerce Low Stock Alerts
- Woocommerce Marketplace Stripe Connect
- Woocommerce Gift Cards Pro
- Woo Direct Checkout
- Linnworks Wp
- Mailchimp For Woocommerce
- Woocommerce Cod Fee
- Woocommerce Wholesale Prices
- Woocommerce Cart Abandonment Recovery
- Woocommerce Mirakl
- Funnelkit Stripe Gateway
- Yith Woocommerce Product Image Gallery Slider
- Woocommerce Shipment Tracking Pro