SleekView Charts for qTranslate-XT: posts-per-language dashboards
qTranslate-XT stores every language inline inside wp_posts.post_title and wp_posts.post_content using [:en] and [:de] bracket tags, with the enabled language list under qtranslate_options in wp_options. SleekView Charts reads those columns and renders a corpus-wide posts-per-language dashboard inside WP Admin.
♾️ Lifetime License available
From bracket tags to a coverage dashboard, no exports
qTranslate-XT continues the inline tag tradition that started with qTranslate. Every language for a post sits in the same row, wrapped in tags like [:en]Hello[:][:de]Hallo[:][:] inside wp_posts.post_title, wp_posts.post_content, and the excerpt. Enabled languages and the default locale live in wp_options under qtranslate_options, with a serialized array of language codes and labels.
That format keeps editing simple and reporting frustrating. The default Posts list shows one row per post in the admin language only, and the inline tags stay invisible. There is no built-in screen that answers "how many posts are missing the French variant" or "which post type lags behind on Italian" without running SQL against the inline tag presence.
SleekView Charts reads wp_posts directly, parses the qTranslate-XT inline tags using the codes from qtranslate_options, and renders four cards on top of that. A Number for posts missing any enabled language. A Pie split by language coverage. A Bar of coverage per post_type. An Area of qTranslate-XT edits per week from post_modified. The plugin still owns the language switcher and the bracket-tag format. SleekView only reads what is already in the database.
Workflow
From bracket tags to dashboard in four steps
Point SleekView at wp_posts
Switch the view to Charts
Add KPI, language, post-type, and trend cards
Save and share with the localization team
Sample dashboard
Charts you can build from qTranslate-XT data
Posts missing a language
Count
Coverage by language
Count
group by language_code
Translation coverage by post type
Count
group by post_type
qTranslate-XT edits per week
Count
group by post_modified
Comparison
Default qTranslate-XT admin vs SleekView Charts
Default qTranslate-XT admin
- Posts list shows one row per post in the admin language only
- Inline bracket tags inside post_content stay invisible in list views
- No corpus count of posts missing a language variant
- No time-series of translation activity across the team
- Coverage per post type requires custom SQL against the bracket tags
SleekView Charts
- Live KPI counts for posts missing a qTranslate-XT language tag
-
Per-language coverage donut from the
qtranslate_optionscode list - Post-type translation coverage ranked side by side in one chart
- Time-series area for post_modified on rows with bracket tags
- Saved Charts views shared in WP Admin per role
Features
What SleekView Charts gives you for qTranslate-XT
Reads qTranslate-XT bracket tags directly
No re-indexing, no second source of truth. SleekView Charts reads wp_posts.post_content and the qtranslate_options array, parses the bracket tags, and renders the cards on top of them.
Mixed card types on one canvas
Combine Number, Pie, Bar, and Area in a single view. KPIs sit next to distributions, distributions next to trends, all reading from the same qTranslate-XT dataset.
Role-aware visibility
Translators see coverage on their own assigned section, managers see corpus-wide language health. The same Charts view filters per user without rebuilding it.
Audience
Who builds qTranslate-XT dashboards with SleekView
Localization managers
Open one dashboard each week to see the corpus coverage curve, the language pulling the average down, and the post type that still needs an Italian or Spanish pass.
Content editors
Track translation coverage for the section they own without scrolling through hundreds of qTranslate-XT posts or guessing which language tags are missing.
Agencies
Show clients the translation coverage curve trending up each sprint. The Charts view replaces the screenshot deck pulled from the qTranslate-XT admin.
The bigger picture
Why qTranslate-XT needs a Charts layer
qTranslate-XT stores every language inside the same post row using bracket tags, which is exactly what makes its editor experience smooth and its reporting experience hard. The Posts list shows one row per post in the admin language, hiding which language tags are present and which are missing. Localization managers cannot answer "how complete is French across the corpus" without exporting and parsing the inline tags.
SleekView Charts reads the same post_content column, parses the language tags using the codes from qtranslate_options, and renders four cards that answer those questions in one glance. The data is already correct because qTranslate-XT wrote it. Charts just gives the team a dashboard to look at it.
Missing translations cost search traffic in every locale that lags behind, and a live coverage dashboard catches the gap the day a new post lands.
Questions
Common questions about SleekView Charts for qTranslate-XT
No. Charts is a read layer for reporting. SleekView's table view can edit post_content directly if you want, but the Charts module only visualizes the inline qTranslate-XT bracket tags that the plugin has already written to wp_posts.
No. SleekView caches aggregate queries per card and re-runs them on a configurable interval, so charts stay fast even on sites with tens of thousands of posts carrying multiple qTranslate-XT bracket tags in post_content.
Yes. qTranslate-XT add-ons extend SEO and admin handling but every translated string still lands inline in wp_posts or in known wp_postmeta keys, both of which SleekView already reads through the same data source.
Yes. Add one card per metric. Each card is configured independently, so coverage donuts, post-type bars, and weekly edit area can sit side by side on the same WP Admin canvas.
Product titles and descriptions sit in wp_posts the same way, so the same bracket tags apply. The chartCards reading post_content tag presence pick up product post types automatically alongside posts and pages.
Yes. Apply a filter on wp_posts.post_author and the cards re-aggregate for that user only. Multi-translator teams use this to scope each translator's coverage view to their own section.
No. wp_posts stores post_modified per row, so the Area card on qTranslate-XT edits per week reads the existing column filtered to rows whose post_content contains the bracket tags from qtranslate_options.
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 a board report needs the numbers offline.
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
- Yith Subscriptions
- Yith Woocommerce Waiting List
- Abandoned Cart Lite For Woocommerce
- Woocommerce Shipping Fedex
- Woocommerce Show Single Variations
- Woocommerce Shipping Ups
- Woocommerce Square
- Woocommerce Shipping Dhl
- Woocommerce Shipping Pickup Location
- Woo Stripe Payment
- Yith Woocommerce Pdf Invoice
- Wpc Buy Now Button
- Sumo Subscriptions
- Woocommerce Sezzle
- Wpc Fly Cart