Pseudo-events

Mon, 01 Jan 0001 00:00:00 +0000

webtrees has no event bus, so core actions (logins, failed logins, logouts, record edits, errors, searches) are detected by polling the webtrees log table (app/Log.php, table log) and firing an event per new matching log entry. It is off by default: nothing runs until you enable the offered cronjob:pseudo-events job.

Built-in events (one cj_event per new log row, payload = the row):

Event	Log filter (log_type, message prefix)	Fires when
`cronjob:log-auth-failed`	`auth`, `Login failed`	a login attempt failed (wrong password, unknown user, unverified, not approved, no session cookies)
`cronjob:log-auth-login`	`auth`, `Login:`	a user logged in
`cronjob:log-auth-logout`	`auth`, `Logout:`	a user logged out
`cronjob:log-error`	`error`, –	an exception was caught and logged (the message is the trace)
`cronjob:log-edit-update`	`edit`, `Update:`	a record was updated (`GedcomRecord::updateRecord()`)
`cronjob:log-edit-delete`	`edit`, `Delete:`	a record was deleted (`GedcomRecord::deleteRecord()`)
`cronjob:log-search`	`search`, –	a search ran (one log row per searched tree)

Payload: log_id, log_time, log_message (truncated to 250 characters, UTF-8-safe) plus gedcom_id / user_id when the log row carries them. The message prefixes are the hard-coded English strings of the current core; a core update that changes them silently stops the matching event (no fallback by design) — the event catalog descriptions and the test-pseudo-events suite pin the current mapping.

Route events

Mon, 01 Jan 0001 00:00:00 +0000

A complementary, immediate detection mechanism: instead of polling state on a schedule, the module observes the HTTP request itself. When a request to a mapped mutating route has been handled successfully (2xx/3xx), it queues the matching event into the same cj_event queue — a listening event job then reacts at the next tick (~60 s), with no polling latency.

Which routes are mapped — two rules, both derived from the live webtrees route table. Common prerequisites: path starts with /tree/{tree}/, the handler is in webtrees’ request-handler namespace (RequestHandlers in 2.2.6, Controllers in 2.3), and the request is a POST mutation. In 2.2.6 this is enforced at map time (GET page routes are not mapped); in 2.3 the route carries no HTTP method, so the POST check happens at fire-time and the GET form-load of the same route is ignored.

Events on wt-modules

Pseudo-events

Route events