內容簡介
Leenkat Editorial Tracker 是一款專為 WordPress 設計的編輯事件記錄外掛，能夠詳細記錄用戶的編輯與發佈行為，並提供清晰的事件日誌，幫助網站管理者追蹤內容變更與編輯活動。
【主要功能】
• 專屬的編輯追蹤管理選單
• 詳細的事件日誌，包含日期、用戶、行動等
• 今日發佈、編輯及活躍編輯者的摘要卡片
• 可依內容標題、用戶、行動等篩選
• 可配置每頁顯示項目數量
• 角色與用戶基礎的事件日誌存取權限
外掛標籤
開發者團隊
原文外掛簡介
Leenkat Editorial Tracker provides a focused editorial event log for WordPress.
It records the real logged-in user who publishes or edits tracked
content while keeping the assigned WordPress Author separate.
Main features:
Dedicated Editorial Tracker admin menu.
Event Log with date, user, action, content, author, source, and content history.
Summary cards for today’s publications, edits, and active editors.
Filters by content title, user, action, content type, and date
range.
Configurable items per page for large editorial sites.
Dashboard widget showing User, Action, and Content with a View All
Event Log link.
Role- and user-based permissions for Event Log access.
Select which content types and actions are tracked.
Configurable automatic log retention.
Clear Log Now tool for administrators.
Database information showing total, oldest, and newest events.
Optional data deletion on uninstall.
Autosaves and revisions are not counted as editorial edits.
Scheduled publication preserves the user who scheduled the content
when WordPress publishes it automatically.
Event records retain captured user and author names even if those
accounts are later removed.
Event history is preserved when tracked content is permanently
deleted.
The plugin does not reconstruct activity that happened before tracking
began.
All tracking data is stored locally in the WordPress database. The
plugin does not send editorial activity to external services.
Privacy
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.
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.
