Опис
An AI agent, a headless front end, a sync script and a cron job all reach WordPress the same way a person never does: over an API. When something on the site is not what you left it as, the question is not “who changed this” but “did a person change this, or did something else”.
This plugin answers that question and only that question. It records changes that arrived over the REST API, WP-Cron, WP-CLI or XML-RPC. A change made by a person clicking in wp-admin is not recorded – not filtered out afterwards, not stored and hidden, simply never written.
Why not a general activity log
General activity logs record everything, which means the automated change you are looking for is one line in a thousand made by your own team. This one starts from the other end. If you already run an activity log, this sits beside it and answers a different question.
What it records
- 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.
What it does not record
- 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.
Reading the log
On its own admin screen, filtered by channel, object type and date range. Or over the REST API at 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,appanduser_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.
Відгуки
Для цього плагіна немає відгуків.
Учасники та розробники
“Digitizer AI Agent Log” — проект з відкритим вихідним кодом. В розвиток плагіну внесли свій вклад наступні учасники:
Учасники
Перекладіть “Digitizer AI Agent Log” на вашу мову.
Цікавитесь розробкою?
Перегляньте код, перегляньте сховище SVN або підпишіться на журнал розробки за допомогою RSS.
Журнал змін
1.1.0
- 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.
1.0.1
- The plugin page gets its screenshot. No functional change.
1.0.0
- First release.