This patch is to add the acting_user field as a relationship in views. This allows connecting activity logs back to the user who triggered the event. From there, any user information can be accessed, such which groups they are a member of.

CommentFileSizeAuthor
expose_acting_user_views_activity_logs.patch912 bytescashwilliams

Comments

icecreamyou’s picture

icecreamyou commented
Status: Needs review » Closed (works as designed)

The reason this doesn't currently exist is that acting_user isn't accurate for grouped messages. Specifically acting_user will be the UID of the person who generated the first grouped event. Instead of adding relationships through Views, additional information you want to display should be exposed through tokens so that administrators can configure it through the Rules interface, and anything you want to filter on should be exposed as visibility groups because that lets Activity Log take care of filtering grouped messages intelligently. That said, this is the product of a somewhat flawed model, and the preferred approach will change as a result of fixing it (see #1259306: Re-architect activity message visibility). The ideal situation is obviously to support the full power of Views for activity messages, but unfortunately the current message grouping and visibility grouping design doesn't support it well.

ezra-g’s picture

ezra-g commented
Status: Closed (works as designed) » Postponed

this is the product of a somewhat flawed model, and the preferred approach will change as a result of fixing it

I'm moving the status here to postponed since it sound like this is a feature that could be supported after #1259306: Re-architect activity message visibility is completed.