Event history is preserved when tracked content is permanently deleted.<\/li>\n<\/ul>\n\nThe plugin does not reconstruct activity that happened before tracking began.<\/p>\n\n
All tracking data is stored locally in the WordPress database. The plugin does not send editorial activity to external services.<\/p>\n\n
Privacy<\/h3>\n\n
Leenkat Editorial Tracker stores editorial activity locally in the site's WordPress database. Recorded event data can include the acting user's ID and display name, the assigned author's ID and display name, the content ID, content title, content type, action, source, and event time.<\/p>\n\n
The plugin does not transmit editorial activity to Leenkat or to any external service. Administrators can configure automatic retention, clear the log manually, and optionally delete plugin data on uninstall.<\/p>\n\n\n
\n- Upload the plugin folder to
\/wp-content\/plugins\/<\/code>, or install the ZIP through the WordPress Plugins screen.<\/li>\n- Activate the plugin.<\/li>\n
- Open Editorial Tracker > Event Log.<\/li>\n
- Configure display, Dashboard, permissions, tracking, and retention under Editorial Tracker > Settings.<\/li>\n<\/ol>\n\n\n
\nIs the assigned WordPress Author changed?<\/h3><\/dt>\nNo. The assigned Author remains untouched and is displayed separately from the user who performed the editorial action.<\/p><\/dd>\n
Does the plugin reconstruct old publishers or edits?<\/h3><\/dt>\nNo. Activity is recorded only after tracking begins. The plugin does not infer historical publishers from the assigned Author or other metadata.<\/p><\/dd>\n
Are autosaves and revisions counted as edits?<\/h3><\/dt>\nNo. Autosaves and revisions are excluded.<\/p><\/dd>\n
Can I control who can view the Event Log?<\/h3><\/dt>\nYes. Administrators always have access, and additional roles or individual users can be granted access in Settings.<\/p><\/dd>\n
What happens if a tracked post or page is deleted?<\/h3><\/dt>\nIts recorded editorial events remain in the Event Log as historical audit data. The stored content title and captured user\/author names remain available, while the edit link is no longer shown.<\/p><\/dd>\n
What happens if a user account is deleted?<\/h3><\/dt>\nNew events store a snapshot of the acting user's and assigned author's display names at the time of the event, so historical records can remain understandable even if an account is later removed.<\/p><\/dd>\n
Does the plugin support WordPress Multisite network activation?<\/h3><\/dt>\nVersion 1.0.1 is intended for per-site activation. Network-wide multisite activation is not a supported workflow in this release.<\/p><\/dd>\n
Can I limit the size of the log?<\/h3><\/dt>\nYes. You can automatically delete events older than 7, 30, 90, 180, or 365 days, or keep events indefinitely.<\/p><\/dd>\n
What happens when I clear the Event Log?<\/h3><\/dt>\nClear Log permanently removes recorded event rows and resets historical post-level tracking metadata. Pending scheduler attribution is preserved so future scheduled publications can still be assigned to the user who scheduled them.<\/p><\/dd>\n
Does uninstalling the plugin delete the log?<\/h3><\/dt>\nOnly if \"Permanently delete all plugin data on uninstall\" is enabled before uninstalling. It is disabled by default. When disabled, the Event Log and stored tracking data are preserved so they remain available if the plugin is installed again.<\/p><\/dd>\n
Does it track WooCommerce products and Elementor changes?<\/h3><\/dt>\nIf their content type is enabled under Tracked content types, edits can be recorded when either the core WordPress post record or meaningful post meta changes. This covers common meta-based edits such as WooCommerce product data and Elementor page data. WooCommerce orders are intentionally excluded in version 1.0.1 because modern stores may use HPOS and require dedicated order tracking.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.1<\/h4>\n\n\n- Fixed plugin deletion when data preservation is enabled.<\/li>\n
- Clarified the uninstall data-deletion setting and preserved-data behavior.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release.<\/li>\n
- Editorial Event Log and content history.<\/li>\n
- Summary cards and filters.<\/li>\n
- Dashboard activity widget.<\/li>\n
- Display and pagination settings.<\/li>\n
- Role and user permissions.<\/li>\n
- Tracked content type and action controls.<\/li>\n
- Automatic retention and manual log clearing.<\/li>\n<\/ul>","raw_excerpt":"Track who actually publishes and edits WordPress content, independently from the assigned post author.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/366029","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=366029"}],"author":[{"embeddable":true,"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/fajryassin"}],"wp:attachment":[{"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=366029"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=366029"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=366029"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=366029"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=366029"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ta.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=366029"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}