[6.x] Add activity logging foundation - #19496
Merged
Merged
Conversation
📚 Storybook previews@craftcms/ui — open Storybook No changed components detected in this Storybook. resources/js — open Storybook No changed components detected in this Storybook. |
…base # Conflicts: # composer.lock # src/Database/Migrations/Install.php
…base # Conflicts: # composer.lock # src/Structure/Structures.php
Contributor
riasvdv
marked this pull request as ready for review
September 7, 2026 08:58
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Initial backend implementation of activity logging.
Activity event types require implementing a
ActivityEventTypeInterfaceinterface. This allows for plugins to add additional event types with us owning how they are rendered and stored.This PR also adds an initial set of events logged for the most common Element events we'd be interested in:
Activity history has a configurable retention period, with expired events removed during garbage collection.
ActivityActor,ActvitySubjectandActivitySourceand the event's information are stored insnapshotson the activity row's payload. This is to ensure we can always display the activity, regardless of an actor, subject or the event itself no longer being available.changesare stored in a list ofActivityChangeDTOs, witholdandnewvalues, so rendering them will be straightforward and gives a structured and type-safe way for plugin developers to define what has changed.An event type can also own how it's displayed by overriding or implementing the
format(ActivityEvent $event)method.AI docs: https://github.com/craftcms/cms/blob/feature/activity-logs-base/docs/activity-logging.md