Digitizer AI Agent Log
| 开发者 | benkalsky |
|---|---|
| 更新时间 | 2026年9月9日 22:26 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- The channel -
rest,cron,cliorxmlrpc. - Which application password authenticated the request, by name, when there was one. Never a guess: when the name cannot be determined the field is empty rather than filled with a User-Agent or an IP that merely looks like an identity.
- What changed - the object, and which fields were touched.
- When, in UTC, shown in your site's timezone.
- Not the values. The names of the fields that changed, never their contents. A log of what your site contains is a second copy of your site.
- Not people. A block editor save is a cookie-authenticated REST request, and it is recognised as a person and skipped. This is the plugin's central promise, and it is the case it was hardest to get right.
- Not reads. Something polling the REST API would fill the table in a day and drown the writes that were the reason to look.
- No IP addresses.
digitizer-ai-agent-log/v1/activity, which requires manage_options. There is deliberately no route that deletes: a log that can be erased through the API is a log an attacker erases on the way out.
Multisite
Each site keeps its own log, in its own table, and a run that switches between sites files each change under the site it happened on.
安装:
- Install and activate. The log table is created the first time the plugin runs.
- Find the log under Agent Activity in the admin menu.
常见问题:
Does it slow the site down?
Changes are held in memory during the request and written once, at shutdown, and only when the request came in on a channel worth recording. A browser request writes nothing at all.
Does it send anything anywhere?
No. Nothing leaves the site.
How large does the table get?
Old rows are pruned automatically, at most once an hour.
A plugin on my site rewrites its own settings and fills the log. Can I silence it?
Yes, with a filter. Nothing is filtered out by default, because what is absent from this log is supposed to mean it did not happen over an API:
add_filter( 'digitizer_ai_agent_log_record', function ( $record, $entry ) { if ( 'elementor_library' === $entry['object_subtype'] ) { return false; } return $record; }, 10, 2 );
The entry carries object_type, object_subtype, object_id, object_name, action, fields, blog_id, channel, app and user_id, so a rule can match on who made the change as well as what it touched. On a network the filter runs inside the site the change happened on, so a callback may read that site's own options to decide.
Note that such an entry is not a mistake: WordPress refuses an identical meta write before the plugin ever sees it, so a change that reaches the log did alter the row. It is simply a change you may not care about, and only your site can say which those are.
What happens when I uninstall it?
The table is dropped and both of its options are deleted, on every site of a network. Nothing is left behind.
更新日志:
- 1.2.0 recognised only half of Elementor's kit copy. Elementor saves the kit's post row as well as its settings when it mirrors the site name, and that save still produced a "Default Kit" row with no fields beside the option change. Both halves are now recognised for what they are.
- The site tagline (
blogdescription) is recorded when it changes, beside the site name. - Elementor copies the site name and tagline into its active kit whenever they change. That copy no longer gets a row of its own next to the option change that caused it - one action, one row. A kit written on its own, or together with anything else, is recorded as before.
- A
digitizer_ai_agent_log_recordfilter, applied to every entry once the channel and the application name are known, so a site can silence a writer it does not care about. Nothing is filtered by default.
- The plugin page gets its screenshot. No functional change.
- First release.