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

Allow unsubscribing a pending membership #283

Closed
amitaibu opened this issue Aug 2, 2016 · 3 comments
Closed

Allow unsubscribing a pending membership #283

amitaibu opened this issue Aug 2, 2016 · 3 comments

Comments

@amitaibu
Copy link
Owner

amitaibu commented Aug 2, 2016

\Drupal\og\OgAccess::userAccess should check unsubscribe permission even if membership is pending

@pfrenssen
Copy link
Collaborator

Do you think there will ever be any more permissions a pending member could have? For example a group could allow pending members to start interacting with a certain section of the group - to introduce themselves to the group for example.

I'm asking because it would be a different implementation:

  • If pending member can only be unsubscribing and nothing else, this will be a hard coded switch where we check this particular permission and give access accordingly.
  • If potentially more permission can be granted, we can provide a column for the "pending" role in the UI. 'unsubscribe' would be checked by default, but the admins can also decide to grant other permissions. Or even deny pending members from unsubscribing.

I personally think the UI option would be more flexible, and easier to implement and test too :)

@amitaibu
Copy link
Owner Author

amitaibu commented Aug 5, 2016

We should take the simple route here and special case just the unsubscribe.
Meaning - hardcoded switch.

On Aug 5, 2016 10:33 AM, "Pieter Frenssen" notifications@github.com wrote:

Do you think there will ever be any more permissions a pending member
could have? For example a group could allow pending members to start
interacting with a certain section of the group - to introduce themselves
to the group for example.

I'm asking because it would be a different implementation:

  • If pending member can only be unsubscribing and nothing else, this
    will be a hard coded switch where we check this particular permission and
    give access accordingly.
  • If potentially more permission can be granted, we can provide a
    column for the "pending" role in the UI. 'unsubscribe' would be checked by
    default, but the admins can also decide to grant other permissions. Or even
    deny pending members from unsubscribing.

I personally think the UI option would be more flexible, and easier to
implement and test too :)


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#283 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHrC3v9FqrXsU_IWWzxi5sQOMDAuBgLks5qcudNgaJpZM4JbA6b
.

@amitaibu
Copy link
Owner Author

For reference: We no longer have the unsubscribe permission. Instead we special case it and allow it in the unsubscribe logic

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

No branches or pull requests

2 participants