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

Applying the "reply to discussions" permission to a tag may break the "lock" mode #1832

Closed
matteocontrini opened this issue Jul 30, 2019 · 4 comments

Comments

@matteocontrini
Copy link
Contributor

matteocontrini commented Jul 30, 2019

Bug Report

Current Behavior
If you have a tag where you explicitly set that users can reply to discussions, users may be able to reply to discussions that are locked.

Steps to Reproduce

  1. Log in as an admin
  2. Create a new "restriction by tag" for any tag (X) in the Permissions admin page
  3. Set the permission that allows users to reply to discussions with tag X
  4. Create a new discussion with tag X and lock it
  5. Disable and re-enable the lock extension (this is required to reproduce the issue)
  6. Log in as a regular user
  7. Try to reply to the created discussion in tag X and succeed

Expected Behavior
Users should not be able to reply to discussions that are locked (unless they have the "canLock" permission).

Screenshots

Admin view:

immagine

User view:

immagine

Environment
Reproduced on beta.flarum.site and nightly.flarum.site.

@askvortsov1
Copy link
Member

This will be fixed with the policy rewrite I'm working on right now.

@matteocontrini
Copy link
Contributor Author

matteocontrini commented May 25, 2020

Hello, is there a chance to have this fixed for the next beta? It's the only issue marked as "critical" (EDIT: currently) but it's been almost a year since it's been reported... Thanks 😃

@dsevillamartin
Copy link
Member

I think this issue is more complicated than it seems. We've discussed multiple ways on fixing it, and the policy refactor PR may fix it.

@askvortsov1 askvortsov1 self-assigned this Oct 28, 2020
@askvortsov1
Copy link
Member

Fixed in #2461

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

Successfully merging a pull request may close this issue.

6 participants