-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Store user state in Audit Trail on certain user events #17507
Comments
Are you to submit a PR? |
Most likely yes. Though first I want to see if there are any comments or considerations beyond what I've written above. Also @domonkosgabor , any thoughts? |
I like this idea! |
Is this related to having richer user profiles? Because that BTW can be achieved via content items (which have Audit Trail diff support already): https://docs.orchardcore.net/en/latest/reference/modules/Users/CustomUserSettings/ |
Yes, that would be the goal. To clarify, are you talking about content types with the
|
I was thinking about this, yes. I see, so the issue is that such content items are not individual items but part of the |
Security considerations mentioned on the PR |
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues). This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here. |
Is your feature request related to a problem?
Currently if you have attached user settings (name, address, etc) they are not stored in Audit Trail events. (e.g. mentioned here) It would be good to store them on events that trigger when the
User
is changed.Describe the solution you'd like
It would be good to either add an
AuditTrailUserEvent.User
property (for parity withAuditTrailContentEvent.ContentItem
) or to create a separateAuditTrailUserStateEvent
. Whichever makes more sense.It should trigger on
IUserEventHandler
's past tense methods (e.g. onUpdatedAsync
but not onUpdatingAsync
). Unlike the currentUserEventHandler
it should not trigger onILoginFormEvent
to avoid cluttering.Describe alternatives you've considered
I can't think of any.
The text was updated successfully, but these errors were encountered: