Repository navigation
FAQ
The Latin “tabula mea” means “my board”. For this plugin, it also expresses “my overview”: understanding statistics, maintaining content and presenting selected results.
TabulaMea counts visible page loads. Reloading a page counts as a new pageview. Only repeated technical delivery of the same page load, for example after a network error, is not counted twice. Collection exclusions and privacy signals still apply. It does not calculate unique visitors or sessions, track click events or build visitor profiles. Search pages are counted separately only when search reporting is enabled; 404 pages are excluded.
No. It runs independently. Their local tables are needed only for an optional historical import. Choose one source per website; Koko and Statify imports cannot be combined.
TabulaMea does not set statistics cookies or use persistent browser storage for measurement. Statistics are stored locally. Optional country database downloads are separate server connections requiring consent; visitor information is not sent to the database provider.
Administrators by default. Access supports role and personal rules. The compact dashboard widget has separate permissions. Public output and exact public numbers need separate consent switches, and saved rankings also require individual publication.
No. Data-minimizing technology does not replace review of your website, hosting and configuration. The privacy text suggestion describes TabulaMea, needs review, and is neither a complete privacy policy nor legal advice.
Logged-in administrators and editors are excluded by default. Do Not Track, Global Privacy Control, browser blocking and disabled JavaScript can also prevent collection. Private windows may send privacy signals too. The guided test under Overview intentionally creates no regular pageview.
Collection methods, scope, bot filters, privacy signals and browser blocking differ. Referrer information is not always available. TabulaMea counts pageviews, not unique people, so avoid comparing these directly with visitor or session totals.
An absent record may mean little or no traffic, or interrupted collection. Dotted lines do not estimate intermediate values. A dash in a content column means no aggregate is available for that period. Chart help and the values table explain the available records.
Its count can continue increasing until the end of the day. Dates and times follow the website configuration. The last accepted pageview timestamp is refreshed at most every five minutes.
Yes. Measurement can select public content types and overview/archive groups. The website total then represents that scope. Changes affect future collection; retained historical totals remain.
Enable the pageview column for pages under Content lists. Choose a period in the Pages list and sort by pageviews. Posts and other public content types work similarly. Showing a column does not enable additional collection.
Check dates, content type, exclusions and minimum counts. Comparison methods need preceding records; monthly methods need sufficient views in every complete month. Output includes only currently public content without passwords.
Create a posts ranking, choose a calendar year and item count, such as ten. Review coverage, then optionally save a snapshot and use copy or print output. A separate publication-year filter limits posts by when they were published.
Results, dates and the original ranking definition. Content no longer public is still omitted when rendering, so a snapshot is not an immutable copy of every later content state.
Yes. Total pageviews and dates remain mandatory; other modules are optional. Administrators set site defaults and which modules users may choose. If personal adjustments are allowed, users can change and reset their widget. A compact widget is also available.
Access must allow both public output and exact public counts. A content-specific counter also needs a suitable WordPress content context; otherwise use the whole-site counter. Then check whether your period contains data.
Yes. Recorded counts remain available to authorized admin users. Public presentation has a separate choice: show the ranking order alone, or also display its counts. Saved rankings need individual publication; public counters need number permission.
Output controls live in the block sidebar, with previews in the canvas. The counter supports text before and after the number and native appearance options where supported by the theme. The content-loop variation uses normal Query Loop layout blocks.
Optional categories start when enabled; historical pageview totals alone do not contain that information. Categories below five views are suppressed for the selected period. Allow at least 30 days for an initial picture; small sites may need longer.
Choose non-personal phrases in advance, such as Donations or Become a member. Only exact matches after normalizing case and whitespace receive term counts. Other arbitrary search input is not retained. Overall search usage is counted separately.
If only Donations is selected, donations matches it. Donations wanted does not match unless that entire phrase is selected separately. There is no automatic synonym or topic classification. Terms appear from five views in the period.
Source tables stay unchanged. TabulaMea keeps permanent import receipts and excludes dates from its first own collection day onward. Supported repeats of the same source add eligible new values only. Resetting or replacing source data can break that association. Back up first, pause both collectors and review the preview; there is no automatic undo.
CSV exports bounded report outputs. Configuration transfer applies suitable settings and ranking definitions after preview. Statistics import reads supported historical Koko or Statify data. None replaces a complete WordPress database backup.
Yes, including network activation. The main site and subsites keep separate statistics and settings. Network defaults cover widget display and adjustment limits; local choices win. A combined network-wide statistics report is not provided.
Deactivation preserves data. Uninstall removes plugin-owned temporary data and tasks; permanent statistics and settings remain by default. Only the explicit deletion option removes the relevant website’s permanent TabulaMea data. Other plugins’ data is never deleted.
TabulaMea · Documentation / Dokumentation
Wiki home / Wiki-Startseite · Repository · Downloads & Releases
Help & bugs / Hilfe & Fehler · Discussions / Austausch · Security / Sicherheit
© 2026 David Decker – DECKERWEB.
Plugin: GPL v2 or later / GPL v2 oder höher.