SleekView for Transposh: translation rows as tables
Transposh stores every cached translation in transposh_translations, alongside translator user id, source, and language. SleekView reads that table directly so machine, community, and editor contributions surface as one filterable workspace.
♾️ Lifetime License available
Audit Transposh contributions cleanly
Transposh stores cached translations in a single table, transposh_translations, with columns for original string, language code, translation, source (machine or user), and translator id. The plugin's own admin gives a chronological log of recent edits, which is fine for moderation but not for auditing months of community contributions across multiple languages.
SleekView reads transposh_translations directly and exposes each row with original, language, translation, source, contributor, and timestamp as sortable columns. Filters like source = community, or language = es, or contributor = user_id 12, become saved views that reload instantly.
Edits route through Transposh's own API, which respects the plugin's moderation rules and updates the cache the same way the front-end translation bar does. The grid is purely an audit and bulk-moderation surface on top of the existing table.
Workflow
From recent-edits log to a moderation grid
Connect transposh_translations
transposh_translations and loads original, language, translation, source, and contributor as filterable columns.
Group by source and language
Save moderation views
Bulk-approve or revert
Sample columns
A typical Transposh translation view
transposh_translations with source and contributor.
transposh_translations
| Original | Language | Translation | Source | Contributor | Updated |
|---|---|---|---|---|---|
| About us | DE | Ueber uns | Community | user_12 | Apr 24 |
| Add to cart | FR | Ajouter au panier | Editor | user_3 | Apr 20 |
| Free shipping | ES | Envio gratis | Machine | system | Apr 12 |
| Old promo | IT | (empty) | Missing | n/a | Feb 02 |
Comparison
Default Transposh admin vs SleekView
Default Transposh admin
- Recent-edits log shows chronological entries, not filterable status
- No saved views for community vs machine coverage
- Filters by contributor reset between sessions
- Per-language audit requires scrolling rather than columns
- No bulk-approve from the audit screen
SleekView
-
Every row of
transposh_translationsas a queryable table - Filter by source = community, editor, or machine in one click
- Saved views per language, contributor, or moderation status
- Inline edits route through the Transposh moderation API
- CSV export of community contributions for recognition reports
Features
What SleekView gives you for Transposh Translation Filter
Every translation as a row
Rows from transposh_translations surface with original, language, translation, source, and contributor as sortable columns.
Find community contributions
Save a view for source = community per language so reviewers can verify and approve community translations without opening the recent-edits log.
Bulk-moderate
Approve or revert multiple rows from the grid. Writes go through the Transposh moderation API so the front-end cache stays consistent.
Audience
Who uses SleekView for Transposh
Community moderators
Filter transposh_translations by source = community and verify contributions in a grid instead of scrolling a recent-edits log.
Localization leads
Track contributor coverage across languages and recognise top contributors with concrete counts from the contributor column.
Site owners
Identify still-machine output on high-traffic pages and prioritise human review by sorting on language and original string.
The bigger picture
Why community translation needs a real moderation surface
Transposh's defining feature is community translation: anonymous and registered users can suggest improvements directly from the front end, and those suggestions land in transposh_translations as new rows with a source flag. That feedback loop is the magic of the plugin, but it also produces a steady stream of contributions that someone has to moderate. The default recent-edits log handles a few entries a day, but a popular community site can see hundreds of edits in a week, across half a dozen languages, with mixed quality.
Treating the cache as a queryable, filterable grid is what makes moderation sustainable. A community moderator opens a saved view for source = community in French, works the rows top to bottom, and approves or reverts in bulk. Localization leads recognise top contributors by querying the contributor column.
Site owners spot which high-traffic strings are still machine output and queue them for human review. The grid is purely an audit layer; the front-end translation bar still drives every contribution through Transposh's own moderation API. The result is that the community-translation model scales past the recent-edits log without changing how Transposh works on the public side.
Questions
Common questions about SleekView for Transposh Translation Filter
Transposh keeps all cached translations in a single table, transposh_translations, with original string, language, translation, source flag, and translator id.
No. Transposh's translation engine, community contributions, and front-end translation bar do the actual work. SleekView is the audit and moderation grid on top of the cache.
Yes. Contributor user id is a column in transposh_translations, so views like contributions-by-user_12-in-March save and reload with one click.
Yes. Multi-select rows in the grid and apply approve or revert. Writes go through the Transposh moderation API so the front-end cache updates correctly.
No. The translation bar still reads transposh_translations directly and respects the same moderation flags. SleekView only changes the admin audit surface.
Yes. Filter by source = community and export the visible columns. The CSV is useful for recognition reports or for migrating to a different translation plugin if needed.
Yes. Anonymous contributions appear with whatever contributor identifier Transposh stores (often 0 or a guest token). The grid treats those as a separate group for moderation.
Yes. Filter by source = machine to surface every cached row that has not been touched by a human reviewer, then prioritise by original-string frequency.
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
- Woocommerce Waitlist
- Woocommerce Side Cart
- Woocommerce Affiliatewp Integration
- Woocommerce Quaderno
- Stitchlabs Wp
- Funnelkit Cart
- Woocommerce Recently Viewed
- Woocommerce Min Max Quantities
- Bigcommerce Bridge
- Woocommerce Marketplace Stripe Connect
- Woocommerce Variation Stock
- Woocommerce Product Bundles
- Woocommerce Attribute Swatches
- Woocommerce Coingate
- Woocommerce Colissimo