Filtering activity display based on ACL as opposed to UserID

Is this possible and if so what code would have to be changed in the plugin?

Filter activity where? Please be more specific what you're trying to do.

I'm sorry, I thought it was obvious and now that I read it back later, I realize it really wasn't.:blush: I know you have a lot of posts to read and reply to in a day; I'm sorry I wasn't concise. I went back and changed the post title to reflect this better.

Let me restate: In the CB Activity Module, what changes or additions would I have to make to have it show everyone but a single ACL group (or possibly 2-3 ACL groups)? This wouldn't necessarily have to be able to be changed from the admin side of the module; my thought is that if I selected "Everyone" from the module options, the new code would be used to filter that choice by the ACL group or groups I manually change in the code.

In your opinion would this be a major modification or a few lines of code changed/added?

I see, there is no such feature. Activity has no ACL at all. So yes this would be a massive modification of the plugin. Activity access is done on a per entry basis. For example if the activity entry is a CB ProfileBook entry it checks to make sure the viewing user can even see the CB ProfileBook tab and if they can't the activity is removed.

I see it's more involved than I thought - I tried peeking at the code, but got kinda lost; now I know why.

For now, I think I have found a human engineering solution to resolve this with the client and I'm limiting the display to self and connections. But if you think this would be worth it, I'd be interested in a quote; you can PM and we can discuss if the price would be any more reasonable if I was willing to give the modified version back to the community to use.

Thanks again, Kyle.

We don't do contract development, sorry. There are also no plans to implement ACL for it as it's not needed. Activity is to be controlled by the activity setter. For example CB Blogs activity access is controlled by the viewing users ability to access that particular blog entry.

If you're only wanting to display activity of users that have a specific usergroup you maybe able to add this by modifying the where query usage, but typically that won't work too well as user ACL is quite complex and you'd have to build and test against ACL for every user being display which will probably turn into hundreds of DB queries being made.

Next release will have support for CB Privacy though and will check activity entries against user privacy rows. CB Privacy has some powerful internal caching so this will be pretty efficient and should have no performance impact. This still won't help displaying activity of a specific usergroup though, sorry.