SleekView Charts for Transposh: translated-strings dashboards
Transposh writes every translated string to its own wp_transposh_translations table with the original, the translation, the language code, and the translator user ID, plus a log table for history. SleekView Charts reads those tables and renders translated-strings dashboards inside WP Admin without spreadsheets.
♾️ Lifetime License available
From the Transposh translations table to a dashboard
Transposh stores every translated string as its own row in wp_transposh_translations with columns for original, translated, lang, translated_by, source, and a timestamp, plus a longer history log in wp_transposh_translations_log. The translator can be a human user ID, an anonymous IP hash, or an automatic translation engine code. The admin offers a translation table view inside WP Admin and a search box, but the corpus rollups live outside any default screen.
That structure is great for fine-grained edits and weak for reporting. The default Transposh admin lists one row at a time and confirms whether a single string is translated, but it does not answer "how many strings are still automatic and never reviewed" or "which language has the most human translations from this team" without exporting the table.
SleekView Charts reads wp_transposh_translations joined to wp_users on translated_by and renders four cards on top of that. A Number for total translated strings. A Pie split by target language. A Bar of strings per human translator. An Area of new translations per week. The plugin still owns the inline translation UI and the engine routing. SleekView only reads the rows the plugin has already written.
Workflow
From the translations table to dashboard in four steps
Point SleekView at wp_transposh_translations
Switch the view to Charts
Add KPI, language, translator, and trend cards
Save and share with the localization team
Sample dashboard
Charts you can build from Transposh data
Total translated strings
Count
Translations by target language
Count
group by lang
Strings per human translator
Count
group by translated_by
New translations per week
Count
group by timestamp
Comparison
Default Transposh admin vs SleekView Charts
Default Transposh admin
- Translation table view lists one string per row with no roll-up
- No native count of total translated strings across languages
- Translator activity is not surfaced anywhere in WP Admin
- No time-series of new translations across the team
- Language mix per translator requires exporting the table
SleekView Charts
-
Live KPI counts for total rows in
wp_transposh_translations -
Language mix as a donut from the
langcolumn - Per-translator activity ranked side by side in one chart
- Time-series area for new translations from the timestamp column
- Saved Charts views shared in WP Admin per role
Features
What SleekView Charts gives you for Transposh Translation Filter for WordPress
Reads Transposh tables directly
No re-indexing, no second source of truth. SleekView Charts queries wp_transposh_translations and wp_transposh_translations_log and joins to wp_users to render the cards directly on top of them.
Mixed card types on one canvas
Combine Number, Pie, Bar, and Area in a single view. Volume KPIs sit next to language splits, language splits next to translator activity, all from the same Transposh dataset.
Role-aware visibility
Translators see only their own activity, managers see the team-wide rollup. The same Charts view filters per user without rebuilding it for each role.
Audience
Who builds Transposh dashboards with SleekView Charts
Localization managers
Open one dashboard each week to see the language mix, the most active translators, and the translation volume trend across the team without exporting the Transposh table.
Translators
Track their own translated-strings counter and weekly trend without leaving WP Admin or scrolling through the full Transposh translation table looking for their rows.
Agencies
Show clients translator productivity and language coverage curves each sprint. The Charts view replaces a CSV dump from the Transposh table sent over by email.
The bigger picture
Why Transposh needs a Charts layer
Transposh already records the data that drives any translation report: every string, every language, every translator, every timestamp. The default admin shows that data one row at a time inside a paginated table and confirms whether a single string is translated. Neither the admin nor the WordPress dashboard answers "how many strings did the team translate this month" or "which translator is carrying the German backlog" without an export.
SleekView Charts reads the same wp_transposh_translations and wp_transposh_translations_log, joins to wp_users, and renders four cards that answer those questions in one glance. The data is already correct because Transposh wrote it. Charts just gives the team a dashboard to look at it.
Translator productivity that nobody can see does not get celebrated or rewarded, and a live activity dashboard makes it visible.
Questions
Common questions about SleekView Charts for Transposh Translation Filter for WordPress
No. Charts is a read layer for reporting. The Transposh inline UI and the translation table editor still own all translation edits. SleekView only visualizes the wp_transposh_translations rows the plugin has already written.
 No. SleekView caches aggregate queries per card and re-runs them on a configurable interval, so charts stay fast even on sites with millions of rows in wp_transposh_translations and a long Transposh log history.
 Yes. Transposh stores the translated_by value as a user ID for humans and a known marker for automatic translation, so cards filtered to translated_by greater than zero only count human translations and isolate automatic ones.
 Yes. Add one card per metric. Each card is configured independently, so a language donut and a translator bar can sit side by side on the same dashboard.
 WooCommerce strings translated by Transposh land in the same wp_transposh_translations table with the same lang column. The chartCards reading the table pick up product strings automatically alongside theme and content strings.
 Yes. Apply a filter on translated_by and the cards re-aggregate for that user only. Multi-translator teams use this to scope each translator's view to their own activity.
 No. wp_transposh_translations stores a timestamp per row and wp_transposh_translations_log preserves the full history, so the Area card on new translations per week reads existing columns without an extra log.
 Yes. Each Charts card has a CSV export so you can hand the raw aggregate off to a spreadsheet or BI tool when stakeholders want it outside WP Admin or when payroll needs translator counts.
 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 Product Recommendations
- Yith Woocommerce Ajax Product Filter
- Shipment Tracking
- Woocommerce Eu Vat Assistant
- Woo Checkout Field Editor Pro
- Advanced Dynamic Pricing For Woocommerce
- Yith Woocommerce Popup
- Checkout Plugins Stripe Woo
- Woocommerce Table Rate Shipping
- Yith Woocommerce Questions And Answers
- Wpc Grouped Product
- Woocommerce Quickbooks
- Checkout Manager For Woocommerce
- Woocommerce
- Yith Woocommerce Gift Cards