Dragon Activity Log – Audit Log, User Activity Tracking & Security Audit Trail
A tamper-evident activity log for WordPress. See who changed what, when, and from where, with field-level before/after detail.
Mit Vorsicht verwenden
Dragon Activity Log works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.
- Getestet mit dem neuesten WordPress (7.1)
- Kleine Benutzerbasis (<10 aktive Installationen)
- Bisher sehr wenige Bewertungen
Wie stapelt es sich?
Side-by-side bei Installationen, Updates, Bewertungen und SupportTägliche Downloads
Download-Spitzen folgen normalerweise einer neuen Version - jede Website, die automatisch aktualisiert wird, gilt als Download.
Ranglisten
Where Dragon Activity Log stands todayWordPress.org Ranglisten suchen
Live-Position in der Plugin-Suche, Top 100| Stichwort | Position |
|---|---|
| Activity Log | >100 |
| Audit-Log | >100 |
| audit trail | #77 |
| Sicherheit | >100 |
| user activity | >100 |
About Dragon Activity Log
Aus der offiziellen Readme · V1.1.0Beschreibung
Dragon Activity Log records what happens on your WordPress site in a fast, searchable audit trail that lives in its own database table. Unlike a plain event list, it shows the field-level change for the fields listed below (the old role and the new role, the old setting value and the new one, a renamed title or slug), and it links every event to the one before it with a SHA-256 hash so that a later edit or deletion of the log can be detected.
Everything in this plugin is free and fully functional: every event type, no cap on the number of events stored, any retention window including “keep forever”, all filters and search, live updates, integrity verification, one-click rollback of settings and role changes, full before/after diffs, security alert emails, CSV and JSON export, WooCommerce events, and the WP-CLI commands. (Individual values in the change detail of a log row are shortened at 500 characters; the full diff keeps the whole value.)
Why Dragon Activity Log
- Field-level change detail – before and after values for post title, slug and excerpt, user email, display name, URL and roles, media title, caption and alt text, and single-value settings (array settings show their item count, and a post body is flagged as changed in the row)
- Full before/after diffs – “Full details” on a post or setting event opens a side-by-side diff of the whole post content, title, excerpt and status, or of the whole setting value, kept from the moment of the change
- One-click rollback – put a changed setting back to its previous value, or undo a role change, from the same dialog. A rollback only runs while the setting or the user’s roles still hold exactly what the event left behind, follows WordPress’s own rules for who may change roles, and is itself recorded in the chained log
- Security alerts by email – a login from an IP address the user has not used before, a burst of failed logins from one address, and a user made administrator (or super admin on a network), sent to the site admin email or a list of addresses you choose. Off until you switch them on
- CSV and JSON export – download the events that match the filters on screen; spreadsheet formulas in exported cells are neutralised, and every export is itself logged
- WooCommerce events – new orders, order status changes, stock quantity and stock status changes, and new coupons, recorded while WooCommerce is active
- Tamper-evident hash chain – every event is chained to the previous one; one click checks the chain (up to 25 seconds in the browser; the WP-CLI command checks a log of any size end to end) and reports the first event whose link no longer matches
- Off-site anchor – email (and optionally post to a signed webhook) the chain head daily or weekly, then compare the log against any anchor later: proof that the log was not rewritten, even by someone with database access
- Site Health – an integrity test and an anchor test on the Site Health screen, plus a debug-information section
- Fast and lean – events live in their own indexed table, never in your posts table, and are pruned automatically on the retention window you choose
- Live activity stream – new activity appears on the log screen as it happens
- Privacy controls – capture, anonymize or skip IP addresses, and exclude trusted roles from logging
- Privacy tools integration – events caused by a user, events about their account, failed logins against their username or email, and events about comments they wrote (guests included) are covered by WordPress personal data export and erasure requests
- WP-CLI –
wp dragon-activity-log list,prune,anchorandverify
What gets logged
- Logins – successful logins, logouts, failed logins, password resets
- Users – registration, profile changes, role changes, deletion, and on multisite removal from a site and super admin grants and revocations
- Content – posts, pages and custom post types: create, edit, status change, trash, restore, delete
- Plugins and themes – activate, deactivate, install, update (and a failed single update), delete, switch
- Settings – WordPress and plugin option changes and deletions, with secret-shaped values redacted (option writes made by background cron tasks are skipped unless they touch core settings)
- Media – uploads, title, caption and alt text edits, deletions
- Taxonomies – term create, edit and delete for categories, tags, menus and custom taxonomies
- Comments – submitted, approved, unapproved, spam, trashed, deleted
- Core – WordPress core updates and content exports
- WooCommerce (while it is active) – new orders, order status changes, product stock quantity and stock status changes, new coupons. Orders are no longer also logged as posts on stores that keep orders in the posts table, and a new coupon is logged once as a coupon (its later edits as post events). Store events recorded with no logged-in user (a guest checkout, a payment gateway callback or a scheduled task) keep no IP address
- The log itself – clearing, retention cleanup, anchors, exports, rollbacks and failed alert deliveries
WP-CLI
wp dragon-activity-log list [--limit=<n>] [--event=<code>]wp dragon-activity-log prunewp dragon-activity-log anchor– send an off-site anchor nowwp dragon-activity-log verify [--anchor=<reference>]
Externe Dienste
This plugin does not connect to any external service of ours or of any third party. All logging, hashing and verification runs on your own server.
The optional off-site anchor sends the chain head (an event number, a hash, your site URL and a timestamp; never any event data) to a destination you configure: by email through your site’s normal mail delivery, and, only if you enter a webhook URL, by an HTTPS POST to that URL. Nothing is sent unless you turn the anchor on.
The optional security alerts send an email through your site’s normal mail delivery to the site admin email or the addresses you list. An alert names the site, the user concerned, the acting user or the attempted username, and the IP addresses involved (a burst alert can list several), and links to the activity log. Nothing is sent unless you turn the alerts on.
Credits
The WordPress.org listing icon is drawn with glyphs from Lucide (https://lucide.dev), ISC License. Copyright (c) for portions of Lucide are held by Cole Bemis 2013-2022 as part of Feather (https://feathericons.com, MIT License). All other copyright (c) for Lucide are held by Lucide Contributors 2022. The plugin itself does not include these icons.
Datenschutzerklärung
Dragon Activity Log stores activity data locally in your WordPress database, including usernames, IP addresses (unless disabled or anonymized), and details of changes made on your site. It does not send any data to third parties. IP capture can be disabled or anonymized in the settings. WooCommerce events recorded with no logged-in user (a guest checkout, a payment gateway callback or a scheduled task) are stored without an IP address, because they cannot be matched to a person’s email address. WordPress personal data export and erasure requests are matched by email address and cover events caused by the user, events about their account, failed logins against their username or email, and events about comments written with that email (so guest commenters are covered too). Events about comments that have since been deleted can no longer be matched to an email address.
Installation
- Upload the
dragon-activity-logfolder to/wp-content/plugins/, or install it from the Plugins screen. - Aktivieren Sie das Plugin über den Plugin-Bildschirm in WordPress.
- Go to Tools > Activity Log. Events start recording immediately; the Settings tab holds retention and privacy options.
Änderungsprotokoll
Closes a way to hide an edited event from the integrity check and the off-site anchor. Retention cleanup now checks the chain first and pauses if it is broken. Recommended for everyone.
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=idsprinted “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.
Screenshots
Für Entwickler
Ist das dein Plugin? Zeigen Sie die Zahlen.
Fügen Sie Ihrer Website, Docs oder GitHub Readme ein Live-Badge hinzu. Es wird von selbst aktualisiert - kein Konto erforderlich.
Best Dragon Activity Log alternatives
All Activity Log plugins →Fragen und Antworten
Dragon Activity Log: quick answers
Gerade Antworten, gezogen von Live WordPress.org Daten.
Quelle: WordPress.org
Is Dragon Activity Log free?
Yes. Dragon Activity Log is free to download and use from the official WordPress.org plugin directory.
Is Dragon Activity Log safe to use in 2026?
Dragon Activity Log works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.
How many websites use Dragon Activity Log?
Dragon Activity Log is active on <10 WordPress websites and has been downloaded 626 times since it launched in September 2026. It was downloaded 99 times in the last 30 days.
Does Dragon Activity Log work with WordPress 7.1?
Yes. The developer has tested Dragon Activity Log up to WordPress 7.1.5, the latest release. It requires WordPress 6.2 or newer.
What PHP version does Dragon Activity Log need?
Dragon Activity Log requires PHP 8.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Dragon Activity Log last updated?
The latest version, 1.1.0, was released on October 10, 2026 (1 month ago).
Who makes Dragon Activity Log?
Dragon Activity Log is developed and maintained by Dragon Core.
What are the best alternatives to Dragon Activity Log?
The most popular alternatives to Dragon Activity Log are WP Activity Log (300K+ installs), Activity Log (200K+ installs) and Stream (70K+ installs).
Angetrieben von PageForge
Eine Vorlage und eine Tabelle. Eine echte Seite für jede Suche.
PageForge Verwandelt jede Zeile eines CSV in eine WordPress-Seite mit eigenem Titel, URL, SEO Felder und Schema entworfen. Kostenlos auf WordPress.org.
- CSV und XLSX, plus Google Sheets auf Beruf und Unternehmen
- seinen eigenen Titel, URL, SEO Felder und Schema für jede Seite
- Arbeitet mit dem Blockeditor, Elementor, Divi und Avada
- Kostenlos auf WordPress.org, keine Kreditkarte
