Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
Minds Frontend
Minds Frontend
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 797
    • Issues 797
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 49
    • Merge Requests 49
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Packages
    • Packages
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Minds
  • Minds FrontendMinds Frontend
  • Issues
  • #292

Closed
Open
Opened 3 months ago by Jake Passi@JakePassi
  • Report abuse
  • New issue
Report abuse New issue

(bug): users which have been removed from a group can still post if they don't refresh

Summary

Users which have been removed from a group can still post if they don't refresh.

Steps to reproduce

  1. Create a group with your primary account.
  2. Have your secondary account join the group.
  3. Have your primary account remove your secondary account from the group.
  4. Without refreshing, have your secondary account create a post in the group.

Platform information

Chrome/Win10

What is the current bug behavior?

Users which have been removed from a group can still post if they don't refresh.

What is the expected correct behavior?

Users which have been removed from a group but haven't refreshed yet should get an error message if they try to post, comment or vote on a post in the group.

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Please solve the reCAPTCHA

We want to be sure it is you, please confirm you are not a robot.

Related issues
0

    Related merge requests
    1
    • [Sprint/Subscribers] (bug): Users no longer able to post in Group after being removed.
      !161
    • Jake Passi @JakePassi added 1 - High P - Groups T - Bug labels 3 months ago

      added 1 - High P - Groups T - Bug labels

    • Ben Hayward @benhayward.ben assigned to @benhayward.ben 3 months ago

      assigned to @benhayward.ben

    • Ben Hayward @benhayward.ben changed weight to 5 3 months ago

      changed weight to 5

    • Ben Hayward @benhayward.ben unassigned @benhayward.ben 3 months ago

      unassigned @benhayward.ben

    • Ben Hayward
      Ben Hayward @benhayward.ben · 3 months ago
      Developer

      I think that this can be fixed in the function interact, at ln:194 of engine/Core/Security/ACL.php. Need to add a check that the user is not banned from posting.

      Edited by Ben Hayward 3 months ago
    • Mark Harding @markeharding assigned to @benhayward.ben 3 months ago

      assigned to @benhayward.ben

    • Mark Harding @markeharding changed milestone to %sprint: QA 3 months ago

      changed milestone to %sprint: QA

    • Mark Harding @markeharding added S - Backlog label 3 months ago

      added S - Backlog label

    • Mark Harding @markeharding changed milestone to %sprint: Remind 3 months ago

      changed milestone to %sprint: Remind

    • Ben Hayward @benhayward.ben changed milestone to %sprint: Subscribers 2 months ago

      changed milestone to %sprint: Subscribers

    • Ben Hayward @benhayward.ben added S - InProgress label and removed S - Backlog label 2 months ago

      added S - InProgress label and removed S - Backlog label

    • Ben Hayward @benhayward.ben added S - Review label and removed S - InProgress label 2 months ago

      added S - Review label and removed S - InProgress label

    • Ben Hayward @benhayward.ben mentioned in merge request !161 (closed) 2 months ago

      mentioned in merge request !161 (closed)

    • Mark Harding
      Mark Harding @markeharding · 3 hours ago
      Owner

      @benhayward.ben can you replicate this issue on production?

    • Ben Hayward
      Ben Hayward @benhayward.ben · 2 hours ago
      Developer

      @markeharding No I cannot now, but could at the time. closing this and the above MR.

    • Ben Hayward @benhayward.ben closed 2 hours ago

      closed

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    Assignee
    Ben Hayward's avatar Ben Hayward @benhayward.ben
    Assign to
    None
    Epic
    None
    sprint: Subscribers
    Milestone
    sprint: Subscribers
    Assign milestone
    None
    Time tracking
    No estimate or time spent
    None
    Due date
    None
    4
    Labels
    1 - High P - Groups S - Review T - Bug
    Assign labels
    • View project labels
    5
    Weight
    5
    Confidentiality
    Not confidential
    Lock issue
    Unlocked
    3
    3 participants
    user avatar
    Ben Hayward
    user avatar
    Mark Harding
    user avatar
    Jake Passi
    Reference: minds/front#292