-
Notifications
You must be signed in to change notification settings - Fork 100
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
regression from 6.1: missing admin function to bulk unsubscribe #27
Labels
Milestone
Comments
Has there been any movement on this issue? |
@mikekuriger, as you see, none has contributed anything yet, such as a patch. |
I take that one. |
ldidry
added a commit
to ldidry/sympa
that referenced
this issue
Apr 26, 2019
ldidry
added a commit
to ldidry/sympa
that referenced
this issue
Apr 26, 2019
ldidry
added a commit
to ldidry/sympa
that referenced
this issue
Apr 26, 2019
ldidry
added a commit
to ldidry/sympa
that referenced
this issue
Apr 26, 2019
ldidry
added a commit
to ldidry/sympa
that referenced
this issue
May 17, 2019
ldidry
added a commit
to ldidry/sympa
that referenced
this issue
May 24, 2019
ldidry
added a commit
to ldidry/sympa
that referenced
this issue
May 24, 2019
ikedas
added a commit
that referenced
this issue
May 28, 2019
Fix #27 — Missing admin function to bulk unsubscribe
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is related to #25 . In 6.1, under the Admin tab of the web UI, when you searched for a user it would not only show all the lists that user was on, but on the far right there were buttons to edit or delete the subscription. This made it really handy to delete all that user's subscriptions after they left the enterprise. Now, that interface just shows all the lists that user is on, forcing you to visit each list separately and remove that user with much more steps.
There also doesn't appear to be a sympa.pl command option to delete a user from all lists, so unlike with #25, there is no other option to do a mass deletion of a user other than to manually visit each list.
The text was updated successfully, but these errors were encountered: