The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I know this can be accomplished via hook_audit_log_it, but it seems like it would be a nice feature for audit_log_filter as well. Can we have the ability to allow logging of specific actions by entity? example, Since Audit log is such a hog on the DB when using db logging... I would like to limit logging to deletions only... I suspect that others out there would like to make this granular to content type as well, so I propose going ahead and adding an interface like that.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | audit_log-add_actions_to_filter_module-2596565-9.patch | 10.76 KB | generalredneck |
| #3 | 2016-01-30_22:14:37-Selection.png | 43.31 KB | generalredneck |
| #3 | audit_log-add_actions_to_filter_module-2596565-3.patch | 10.81 KB | generalredneck |
Comments
Comment #2
attiks commentedWe can change the admin page to do this, can you upload a patch?
Comment #3
generalredneckOk, I've got something...
I changed the administrative user internface to accomidate the data stricture a little better as the fieldsets were getting out of control, but you are welcome to adapt what i have however you want. I added some javascript to make the checkbox tree work out..
I removed the bundles variable because I just store everything in a tree now in the entity_type variable. Also I created and update hook to move data over and combine the two variables into the new format. Lastly, I updated the "log_it" hook to respond to the new format as well.
Let me know what you think.
Comment #4
attiks commentedI had a quick look, it looks good, just wondering if we can do the same for other entities like users?
Comment #5
generalredneckAh I see what I did there... yeah... totally. This late night programming thing got me...
I have some logic in there that says "if it has <=1 bundle, just show the entity". I will have to work around that a bit or just take it out completely.
Comment #6
kmajzlik commentedThis code should use new hook instead of hard defining view/edit/delete.
https://www.drupal.org/node/2636916
Comment #7
generalredneckWill do. Thanks.
Comment #8
attiks commentedComment #9
generalredneckOk So I removed the logic that tries to be smart about bundles and entities when there is only one bundle and just show everything anyway.
Example, User will only ever have 1 bundle, and probably the same with File... but I'm showing the bundle and the actions anyway. I think it's ok though, because if you click the "entity checkbox" it will select every bundle and action that belongs to it anyway, so usability it shouldn't suffer too much.
With that said I also added the options code per @karlos007 in #6 since it's been committed. Lastly, I changed it just a hair by calling ucwords on drupal_map_assoc so that the labels would be "nicer". Fixed some translation issues that may have occurred as well in the interface I created.
Rolled this patch against 564409242c9a72107e36b3ffb5363ae496f465f5
Comment #11
generalredneckare you expecting us to write tests for our features now? or is this something D.O added? as it seems, seems there are no tests in the project.
Comment #12
attiks commented#11 Tests would be nice, but i committed it anyways
Comment #15
kmajzlik commented@generalredneck - please add comment in code for function audit_log_filter_update_7001().
Comment #17
attiks commentedComment to update function added