Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
This patch should improve the approach to saving the module's data, also it is designed to improve a flexibility with logs.
Why should we use entities?
Entity API is the fundamental ideology of Drupal. I'm researched with some of these questions before creating a patch:
1. Separate Storage Backends into submodules - This issue has not been active for the last 8 months, but entity approch allows to override an entity store interface at least (although this issue will require additional development).
2. Provide views integration - Good implementation, but there is to much custom code, Drupal already has a great views implementation and we shouldn't clone to much custom code.
User interface changes
User will be able to create a views with audit log (see. Remaining tasks)
Remaining tasks
Provide a user interface (in progress)
API changes
We will need to add version 2.x because the patch is uncompatible with earlier versions at the moment.
Сonclusion
Our team is now actively developing this module and we are open to suggestions on github:
https://github.com/propeopleua/audit_log
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | interdiff_4_6.txt | 9.02 KB | spheresh |
| #6 | 2936158-entity-integration_1.patch | 37.87 KB | spheresh |
Comments
Comment #2
spheresh commentedComment #3
spheresh commentedComment #4
spheresh commentedCode review & bug fixing.
Comment #6
spheresh commentedRefactoring & small fixes:
- composer package name was changed to correct
- .circleci config was removed as non-required for contrib module
- Error when accessing "/admin/structure/audit_log/settings" fix
Comment #8
spheresh commented