Skip to content
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

New circles are treated as an "all user" activity - but no option for this being on/off #204

Open
putt1ck opened this issue May 23, 2018 · 3 comments · May be fixed by #229
Open

New circles are treated as an "all user" activity - but no option for this being on/off #204

putt1ck opened this issue May 23, 2018 · 3 comments · May be fixed by #229

Comments

@putt1ck
Copy link

putt1ck commented May 23, 2018

On NC13.02, Circles 0.13.6, new circles are being notified to all users but there is no Activity listed for this action. We have only

On events happening in a Circle you belong
Any important event in a Circle you are moderating

  • so (a) what setting controls the "circle has been created" notification and (b) shouldn't it be a separate activity option and (c) does it make sense to tell every user that a new circle has been created anyway?
@putt1ck putt1ck added the bug label May 23, 2018
fgsl pushed a commit that referenced this issue Sep 5, 2018
@fgsl
Copy link
Contributor

fgsl commented Sep 5, 2018

I was reviewing a pull request (#192), because I had a serious trouble in a creation of circle in a database with almost 10 hundreds of users. It was created on record of actitivy for each user, then app Activity got "frozen", while waiting for result of query.

When I read this issue, I understood that it is the same cause. I created a option to disable notification for all seen users, then only current user is nofified by app Actitivy about creation of circle.

@michag86
Copy link

michag86 commented Apr 2, 2020

You can disable activity events for new created circles for all users completely with this command:
occ config:app:set circles --value 0 creation_activity

But this is just a workaround.

@kleener
Copy link

kleener commented Oct 26, 2021

Does the problem still exist?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants