Dragon Activity Log – Audit Log, User Activity Tracking & Security Audit Trail

Өзгөртүүлөр

1.1.0

• New: one-click rollback. “Full details” on a setting change or a role change offers to put it back. It runs only while the setting or the user’s roles still hold exactly what the event left behind, follows WordPress’s rules for who may change roles (you cannot take away your own), and records a “Change rolled back” event in the chained log, even when your role is excluded from logging. A change that created or deleted a setting is not rolled back, and the dialog says so. Restoring a permalink setting has WordPress rebuild its permalink rules (leaving plain permalinks also needs one save of Settings > Permalinks, and the dialog says so).
• New: full before/after diffs. Post and setting events keep a copy of the state before and after the change, so “Full details” shows the whole content or setting value side by side. Copies are deleted with their event.
• New: security alerts by email for a login from a new IP address, a burst of failed logins and a user made administrator or super admin. Off until you switch them on; recipients default to the site admin email. At most one burst alert is sent per window for the whole site, listing the other addresses that reached the limit since the previous one; IPv6 addresses are counted per /64 network.
• New: CSV and JSON export of the events matching the current filters. Cells that would start a spreadsheet formula are neutralised, and each export is logged.
• New: WooCommerce events: new orders, order status changes, stock quantity and status changes, and new coupons. Orders are no longer also logged as posts on stores with legacy order storage, a new coupon is logged once, and creating a product is not logged as a stock change. Store events recorded with no logged-in user (such as a guest checkout) keep no IP address. Declared compatible with High-Performance Order Storage.
• These features were the Dragon Activity Log Pro add-on and are now part of this plugin. If the add-on is still active, deactivate it: until you do, the built-in versions stay off and the log screen says so. Nothing is carried over from the add-on: switch the security alerts on again under Settings after deactivating it, and diffs and rollback cover changes recorded from then on (the add-on’s earlier diffs are not carried over).
• The links and notes pointing to the Pro add-on are gone.

1.0.21

• Fixed: someone with database access could hide an edited event from both the integrity check and the off-site anchor by changing one setting. The chain now refuses that, and anchors whose events were removed are only explained by a matching event recorded in the sealed log itself.
• Retention cleanup checks the chain before it deletes anything, records every cleanup that removes events as an event, and never removes events that are not sealed yet. If the chain is broken, cleanup pauses and the Settings tab and Site Health say so.
• An anchor that can no longer be checked says why and names the event that explains it; it is never shown as a match. The command line exits with 2 in that case and with 1 for a failed or busy check. “Beyond the current chain” is gone: a truncated log now reads as broken.
• A database read error during a check is reported as such, not as tampering or a timeout. A check that finished on its last batch no longer reads as out of time.
• The anchor webhook signing secret is stored encrypted, redirects are not followed, and the last anchor shows whether it was delivered.
• Logging: failed single plugin and theme updates, removal from a network site and super admin grants are recorded; settings saved without a real change, a theme switch’s own bookkeeping and Dragon Pro licence re-checks no longer add rows; a role grant before a role change is kept; settings changed late in a request are recorded.
• Secrets: credentials inside serialized settings are no longer stored, and nested secret keys are redacted before a change reaches an add-on. The anchor webhook address is recorded as its host only.
• Settings: an invalid retention, anchor email or trusted proxy entry is rejected with a message and the previous value is kept, and a setting that could not be saved is reported.
• Privacy export: events about a person that someone else caused no longer include that other person’s IP address or username.
• Uninstall deletes data only when the opt-in is clearly on (1, true, yes or on), not for “false” or “no”.
• Fixed: a search for “0” filtered nothing, very long role names lost the event, list --format=ids printed “Array”, and a proxy that appends a port recorded its own address.
• Each admin action checks its own security token and your permission, and every submitted value goes through WordPress’s own sanitizers.
• A plugin update is logged under the plugin’s new name even when the plugin list was read earlier in the same request.
• Fixed: saving settings with a malformed webhook field no longer writes a PHP warning to the debug log.

1.0.20

• Fixed: since 1.0.11, a change to a setting that holds a secret (an API key, token, licence key or password) was not logged at all. It is now logged as “Changed (value hidden)”, and the secret itself is never stored.
• Setting a secret and then setting it back in the same request is not logged, as there was no net change.

1.0.19

• Anchor checks only accept a clear or privacy erasure recorded inside the sealed log itself, so a gap cannot be hidden by editing a setting. Rewrites still show as a mismatch.
• An anchor due while the log is being resealed is retried 15 minutes later instead of being skipped.
• Anchors made before a Clear log or an erasure report the events as rebuilt or erased, not rewritten.
• Sites upgrading straight from 1.0.0 keep their retention and exclusion settings.

1.0.18

• Anchor checks now say when older events were removed by retention cleanup or a privacy erasure, instead of reporting a broken chain.
• Clear, rebuild and erasure events show readable details.
• Settings that other Dragon plugins use for their own bookkeeping are no longer logged as setting changes.
• Log times follow your site’s date format.

1.0.17

• Every screen, email and alert is now translatable, so community translations from translate.wordpress.org cover the whole plugin. Counts use proper plural forms, and numbers and dates follow your site’s language.
• Clear, rebuild and privacy-erasure events show readable details in the log and the live stream.
• The personal-data export lists changes as readable lines instead of raw data.
• Log times follow your site’s date format.

1.0.16

• Fixed: when one of this plugin’s scheduled tasks needed re-creating, it was scheduled before WordPress had finished loading, which made WordPress log “translation loading was triggered too early” notices that named other plugins. Scheduling now waits until WordPress is ready. The notices only appeared with debug logging switched on.

1.0.15

• An “Upgrade to Pro” link on the Plugins screen, a one-line pointer at the foot of the plugin’s own screens, and a single dismissible note once the plugin has done its job. All three disappear when the Pro add-on is active; nothing in the free plugin is locked or changed.

1.0.14

• Listing only: a clearer WordPress.org title and tags, so people searching for an audit log or user activity trail can find the plugin. No functional changes.

1.0.13

• Adds a one-time WordPress.org review prompt on the Activity Log screen after your first integrity check or anchor. No other changes.

1.0.12

• New: off-site chain anchor. Email the chain head daily or weekly (optionally also to a signed webhook you control), send one on demand, and compare the log against any anchor from the Integrity tab or WP-CLI (verify --anchor=<reference>). Each anchor is recorded in the log itself.
• New: Site Health integration. An “Activity log integrity” test, an “off-site anchor” test, and a Dragon Activity Log section under Info.

1.0.11

• Secret-shaped settings (API keys, tokens, passwords, licences) are no longer read at all when they change or are deleted: the event still records that the setting changed, but the value is dropped at the source and is not passed to add-ons either.

1.0.10

• Integrity chain hardening: the hash now covers the event id and uses an unambiguous encoding, so a row cannot be renumbered or have field boundaries shifted unnoticed. Existing chains are rebuilt once after updating (the log itself is untouched).
• Verification now says exactly what it checked: it reports events not yet sealed, tells you when it ran out of time on a very large log, and no longer reports “intact” when another process held the lock.
• Clearing the log or erasing someone’s data checks the chain first and records the outcome; an erasure that removes nothing leaves the chain alone.
• Retention cleanup removes a contiguous block of oldest events and re-anchors after every batch, so an interrupted run can never leave the chain unverifiable; “Run cleanup now” applies the number in the retention field, saved or not, and says so.
• Optional list of trusted proxy addresses (IPs or CIDR ranges): when set, proxy headers are honoured only for connections from those addresses.
• Screen Options on the log now work: choose how many events to show per page and hide columns; live-stream rows respect hidden columns, keep the page at its size and update the item count.
• Hosts whose database cannot provide advisory locks (for example Galera clusters) fall back to an option-row lock, so sealing and cleanup keep running there.
• The background sealer re-reads the chain state from the database before every write, so a persistent object cache cannot hand it a stale copy.
• The events table is created on first load for any site that never ran activation, not only on admin visits.
• Live-stream rows now show the object type and the field-level change table, exactly like rows rendered on load; a log cleared from another tab reloads open log screens; a lost session shows a message instead of silently stopping; typing a page number in the pagination box works.
• Publishing a draft while editing it records one event carrying both the status change and the field changes (previously the field changes were lost). Role additions and removals, and network user deletions, are recorded.
• Less noise: editor autosaves of a draft, and the two option writes behind a theme switch, no longer add rows (the theme switch itself is still logged). On a network, option changes made while switched to another site are recorded on that site.
• JSON-encoded settings values are summarised like arrays instead of being stored verbatim, so a credential nested inside one never reaches the log.
• Comment status events use translated labels; setting an image’s alt text for the first time logs once.
• Accessibility: the active tab is announced, and change-detail field names are proper row headers.
• A missing events table (restored database, manual drop) is recreated on the next request instead of surfacing database errors.

1.0.9

• The log, integrity check and settings now live on one Tools > Activity Log screen with tabs instead of three separate Tools menu entries. Old links redirect.
• Live updates pause automatically while a filter, search or a page other than the first is active, so filtered views are no longer interrupted by unfiltered rows.
• Severity is shown with the Dragon design system’s tinted pills and row markers, and the integrity and cleanup messages are now translatable.
• New “Run cleanup now” button on the Settings tab applies the retention window immediately.
• Events are no longer recorded before WordPress has finished loading, which fixes a “translation loading triggered too early” notice when another plugin crashed during startup.
• Logins, logouts and password resets are now attributed to the user concerned instead of “System / Guest” (WordPress fires those hooks before it sets the current user), so role exclusions apply to them and privacy export and erasure cover them.
• Personal data export and erasure now include events about the user’s account and failed logins against their username, not only events they caused.
• Media alt text changes are recorded with the old and new value; previously that field never showed a difference.
• Changes to the plugin’s own settings are logged, and clearing the log records a “log cleared” event as the first row of the new chain.
• Date filters use the site’s timezone; the retention field only accepts whole days; the daily cleanup and chain reset now coordinate with the background sealer so a rare overlap cannot leave the chain unverifiable.
• The events table is created on sites that never ran activation (network activation only runs it on the main site) and schema updates apply on upgrade.
• Uninstalling with “Delete all data” opted in now also removes that setting itself, and on a network it runs for every site.
• Network activation creates the events table on every site, and new network sites get one automatically.
• Fresh plugin and theme installs are recorded (previously only updates were); deleted options are recorded too.
• The live stream delivers bursts larger than one page across consecutive polls instead of skipping the middle, and guest rows show the “System / Guest” label.
• The migration of settings from the 1.0.0 option names has been removed; sites still on 1.0.0 start with default settings after updating.

1.0.8

• Retention: the retention setting now accepts 0 to keep events forever. Any retention window, or none at all, is available in the free plugin.

1.0.7

• Security: integrity verification now detects truncation of the newest sealed log entries (deleting the tail no longer passes as “verified”).

1.0.6

• Compatibility: tested up to WordPress 7.1.
• Housekeeping: corrected the contributor name in the plugin readme.

1.0.5

• Accessibility: screen-reader labels on the log filters and table header scopes throughout.

1.0.4

• Data safety: uninstalling the plugin no longer deletes its data unless you explicitly opt in first. A reinstall now picks up exactly where you left off. (New setting.)

1.0.3

• New look: the Dragon design system arrives. A consistent Dragon Core header, cleaner tables, and unified status colours. Purely visual; no behaviour changes.

1.0.2

• Fix: the integrity-chain state is now carried safely on a deactivate then reactivate update (it could previously reset).

1.0.1

• Renamed all option, hook, function and constant prefixes to the unique dragonactivitylog_ / DRAGONACTIVITYLOG_ prefix. Existing settings and the integrity-chain state are migrated automatically on update; the event table is unaffected.

1.0.0

• Initial release.