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

[BUG] User info should not have View All members button on Direct messaging #14036

Closed
knrt10 opened this issue Apr 8, 2019 · 0 comments · Fixed by #14081
Closed

[BUG] User info should not have View All members button on Direct messaging #14036

knrt10 opened this issue Apr 8, 2019 · 0 comments · Fixed by #14081

Comments

@knrt10
Copy link
Contributor

knrt10 commented Apr 8, 2019

Description:

On a direct message with user, View All members button should not be there. Cause when clicked it goes back to a blank screen.

Steps to reproduce:

  1. Go to direct message with user
  2. Click on User info
  3. Click on View All members button

Expected behavior:

Button should not be there

Actual behavior:

Direct message

Server Setup Information:

  • Version of Rocket.Chat Server: 1.0.0-develop
  • Operating System: MacOS
  • Deployment Method: Meteor
  • Number of Running Instances: 0
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 8.11.4
  • MongoDB Version: 3.6

Additional context

On it, will fix this

@knrt10 knrt10 changed the title [BUG] User info should not have View All members button [BUG] User info should not have View All members button on Direct messaging Apr 10, 2019
knrt10 added a commit to knrt10/Rocket.Chat that referenced this issue Apr 10, 2019
knrt10 added a commit to knrt10/Rocket.Chat that referenced this issue Apr 10, 2019
knrt10 added a commit to knrt10/Rocket.Chat that referenced this issue Apr 10, 2019
rodrigok pushed a commit that referenced this issue Apr 27, 2019
* Fixed #14036

* Pass parameter from memberList to userInfo to show back button

* Set membersList title from userInfo

* Add a back button to userInfo
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

Successfully merging a pull request may close this issue.

1 participant