Changeset 3789706
- Timestamp:
- 11/07/2026 02:09:39 PM (2 hours ago)
- Location:
- 404ops-activity-log
- Files:
-
- 6 added
- 2 edited
-
assets/screenshot-1.png (added)
-
assets/screenshot-2.png (added)
-
assets/screenshot-3.png (added)
-
assets/screenshot-4.png (added)
-
assets/screenshot-5.png (added)
-
assets/screenshot-6.png (added)
-
tags/0.21.0/readme.txt (modified) (2 diffs)
-
trunk/readme.txt (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
404ops-activity-log/tags/0.21.0/readme.txt
r3788634 r3789706 29 29 * Choose a finite retention period of up to a hundred years, or keep events indefinitely. The same setting applies to imported history and multisite event cleanup. 30 30 31 = How it works = 32 33 1. A WordPress event, or a change in a supported active plugin, triggers a log entry. 34 2. Activity Log stores the event in your site's database. IP addresses are truncated by default; passwords and password hashes are never recorded. 35 3. An administrator reviews and filters the log or exports matching events as CSV. The daily email digest goes to the site's admin address. AI summaries require Activity Log's AI opt-in and a compatible provider configured through WordPress Connectors. 36 37 Screenshot 5 diagrams this flow, and screenshot 6 shows the local log, email digest and optional data destinations. Screenshots 1–4 show the free plugin's admin screens. 38 31 39 == Installation == 32 40 … … 137 145 3. Settings: retention period, IP address truncation, high-risk event email alerts and roles never logged. 138 146 4. Import history from Simple History, WP Activity Log or Stream. 147 5. How it works: site events become a local activity log for review, CSV export and the daily email digest. 148 6. Data paths: the local log, the daily digest and optional AI and Pro destinations. 139 149 140 150 == Changelog == -
404ops-activity-log/trunk/readme.txt
r3788634 r3789706 29 29 * Choose a finite retention period of up to a hundred years, or keep events indefinitely. The same setting applies to imported history and multisite event cleanup. 30 30 31 = How it works = 32 33 1. A WordPress event, or a change in a supported active plugin, triggers a log entry. 34 2. Activity Log stores the event in your site's database. IP addresses are truncated by default; passwords and password hashes are never recorded. 35 3. An administrator reviews and filters the log or exports matching events as CSV. The daily email digest goes to the site's admin address. AI summaries require Activity Log's AI opt-in and a compatible provider configured through WordPress Connectors. 36 37 Screenshot 5 diagrams this flow, and screenshot 6 shows the local log, email digest and optional data destinations. Screenshots 1–4 show the free plugin's admin screens. 38 31 39 == Installation == 32 40 … … 137 145 3. Settings: retention period, IP address truncation, high-risk event email alerts and roles never logged. 138 146 4. Import history from Simple History, WP Activity Log or Stream. 147 5. How it works: site events become a local activity log for review, CSV export and the daily email digest. 148 6. Data paths: the local log, the daily digest and optional AI and Pro destinations. 139 149 140 150 == Changelog ==
Note:
See TracChangeset
for help on using the changeset viewer.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)